XEP-0003: Fix minor XML issues

xep-0003.xml

@@ -140,7 +140,7 @@
 <section1 topic='Controls'>
   <p>A Jabber client can send various controls to the PASS service via the set to control how the PASS service behaves, how the server handles a listening port.</p>
   <section2 topic='expire'>
-    <p>This tells the server to shut down the port after a specified number of seconds.  After the timeout period, the PASS service MUST send an <iq/> to the JID to tell it that the port has been closed down.  It notifies the client with:</p>
+    <p>This tells the server to shut down the port after a specified number of seconds.  After the timeout period, the PASS service MUST send an &lt;iq/&gt; to the JID to tell it that the port has been closed down.  It notifies the client with:</p>
     <example caption='Notification of expiration'><![CDATA[
 <iq type='set'
     id='pass3'
@@ -163,7 +163,7 @@
     ]]></example>
   </section2>
   <section2 topic='oneshot'>
-    <p>This tells the server to listen once, and then close the port.  Even if the <expire/> has not been met, the <oneshot/> overrides that and shuts down the listening port.  When this happens the server notifies the client with the following packet:</p>
+    <p>This tells the server to listen once, and then close the port.  Even if the &lt;expire/&gt; has not been met, the &lt;oneshot/&gt; overrides that and shuts down the listening port.  When this happens the server notifies the client with the following packet:</p>
     <example caption='Server notifies client of oneshot port closing'><![CDATA[
 <iq type='set'
     id='pass4'
@@ -214,8 +214,8 @@
       </tr>
       <tr>
         <td>400</td>
-        <td>Missing <proxy/> specification.</td>
+        <td>Missing &lt;proxy/&gt; specification.</td>
-        <td>Sent a <close/> w/o a <proxy/></td>
+        <td>Sent a &lt;close/&gt; w/o a &lt;proxy/&gt;</td>
       </tr>
       <tr>
         <td>401</td>
@@ -225,12 +225,12 @@
       <tr>
         <td>404</td>
         <td>Port not found in registry.</td>
-        <td>The <proxy port=''/> was not a defined port.</td>
+        <td>The &lt;proxy port=''/&gt; was not a defined port.</td>
       </tr>
       <tr>
         <td>405</td>
         <td>Proxy IP does not match.</td>
-        <td>The IP sent in the <proxy/> does not match the IP of the pass-service</td>
+        <td>The IP sent in the &lt;proxy/&gt; does not match the IP of the pass-service</td>
       </tr>
     </table>
   </section2>
@@ -258,10 +258,10 @@
   </query>
 </iq>
     ]]></example>
-    <p>Obviously the port is not going to be known, but the IP address will let you authenticate the JID via the PASS service since the PASS service tells you the <client/> information upon a connection.</p>
+    <p>Obviously the port is not going to be known, but the IP address will let you authenticate the JID via the PASS service since the PASS service tells you the &lt;client/&gt; information upon a connection.</p>
   </section2>
   <section2 topic='Denying a Connection'>
-    <p>When a server gets an Incoming Connection notification the client has the right to deny that connection based on the <client/> information that it receives.  It can return an error to the PASS service specifying the <proxy/> port and hangup on the active <client/> connection and start listening again.  This does not affect the <oneshot/> control.  For example:</p>
+    <p>When a server gets an Incoming Connection notification the client has the right to deny that connection based on the &lt;client/&gt; information that it receives.  It can return an error to the PASS service specifying the &lt;proxy/&gt; port and hangup on the active &lt;client/&gt; connection and start listening again.  This does not affect the &lt;oneshot/&gt; control.  For example:</p>
     <p>The PASS service sends you:</p>
     <example><![CDATA[
 <iq type='set'
@@ -298,7 +298,7 @@
       <tr>
         <td>401</td>
         <td>Unauthorized</td>
-        <td>The incoming <client/> does not match the <client/> from the client you want to exchange data with.</td>
+        <td>The incoming &lt;client/&gt; does not match the &lt;client/&gt; from the client you want to exchange data with.</td>
       </tr>
     </table>
   </section2>