XEP-0369: Remove whitespace errors

xep-0369.xml

@@ -289,7 +289,6 @@
     <table caption="Standard MIX Nodes">
       <tr><th>Name</th><th>Node</th><th>Description</th></tr>
       <tr><td>Messages</td><td>'urn:xmpp:mix:nodes:messages'</td><td>For distributing messages to the channel. Each item of this node will contain a message sent to the channel.</td></tr>
-      
       <tr><td>Participants</td><td>'urn:xmpp:mix:nodes:participants'</td><td>For storing the list of participants and the associated nick.  Channel participants are added when they join the channel and removed when they leave </td></tr>
       <tr><td>JID Map</td><td>'urn:xmpp:mix:nodes:jidmap'</td><td>For storing a list of anonymized bare JIDs from the participants node with a 1:1 mapping to the corresponding real JIDs.</td></tr>
       <tr><td>Presence</td><td>'urn:xmpp:mix:nodes:presence'</td><td>For storing information about the availability status of online participants, which may include multiple clients for a single participant.</td></tr>
@@ -420,10 +419,8 @@
 </items>
 ]]></example>
     </section3>
-    
     <section3 topic="Subject Node" anchor="subject-node">
       <p>The subject node publishes the current subject of channel. Subject history is stored in MAM. A single item is stored in this node at a time which MUST contain a "text" element and MAY contain additional text elements. Where multiple text elements are provided, each MUST posses an xml:lang attribute that describes the natural language of the subject.  </p>
-      
       <p>
         Setting and sharing subject uses a message with subject element, in a manner compatible with &xep0045;.  Clients MAY also write or access this node using pubsub. Writes to this node will lead to update of subject by sending messages.   Setting the subject is controlled by configuration; in some channels it may be set by all users and in others restricted to administrators.
         The following example shows the format of a item in the subject node.
@@ -439,7 +436,6 @@
         When a user subscribes to the Subject Node, this will cause the channel to send Subject messages to the user through the MIX Proxy.  This is done on initial user subscription and on subject change.   Clients MAY directly read the channel subject from the Subject Node using PubSub.
       </p>
     </section3>
-    
       <section3 topic="Allowed" anchor="allowed-node">
         <p>
           This node represents a list of JIDs that are allowed to become participants. If the allowed node is not present, all JIDs are allowed. This node is accessed and managed using standard pubsub.  The allowed list is always considered in conjunction with the banned list, stored in the banned node.  Only Administrators and Owners have write permission to the allowed node and are also the only roles that are allows to subscribe to this node.    Each item contains a real bare JID.  The following example shows how the allowed list can specify single JIDs and domains.
@@ -1192,7 +1188,6 @@ the participant is not be subscribed to all nodes associated with the channel (i
       </p>
        <p>
         When the client comes online, it will activate use of the MIX Proxy.    The MIX Proxy will then send full presence status to the client using standard presence messages.   This will enable the client to update presence information for the channel.  Note that this does not need any interaction with the channel.
- 
        </p>
 
     </section3>
@@ -1207,7 +1202,6 @@ the participant is not be subscribed to all nodes associated with the channel (i
       <p>
         The second scenario is when the MIX Proxy needs to load or refresh presence status for a channel.  This will be needed when the MIX Proxy and associated server are started.   This MIX Proxy requests presence update by sending a directed presence stanza to the MIX channel from the user's bare JID. The MIX channel can distinguish this from a presence update, which will always be sent from the clients full JID.   This special presence stanza will send to the MIX Proxy (the user's bare JID) presence for all of the items in the presence node using standard presence stanzas.
       </p>
- 
     </section3>
     <section3 topic="Determining Real JIDs" anchor="usecase-real-jids">
       <p>