diff --git a/xep-0369.xml b/xep-0369.xml
index b5f1197a..b003af55 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -44,6 +44,8 @@
       Various Clarifications from Dave Cridland review:
       Remove Recommendation to do MIX/MUC on separate domains,
       Sort Default JID Visibility Preference,
+      Make Owner optional,
+      Clarify that Nick is optional,
       
     </p></remark>
   </revision>  <revision>
@@ -518,7 +520,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
         <tr><td>Anyone</td><td>Any user, including users in the banned node.</td></tr>
       </table>
       <p>
-        There MUST always be at least one Owner for a Channel.   Administrators, Participants, and Allowed are optional and do not need to be set.  Rights are defined in a strictly hierarchical manner following the order of this table, so that for example Owners will always have rights that Administrators have.
+        There MUST always be at least one Owner for a Channel.   Owners, Administrators, Participants, and Allowed are optional and do not need to be set.  Where no owner is explicitly set, it is anticipated that a server administrator will have owner rights.   Rights are defined in a strictly hierarchical manner following the order of this table, so that for example Owners will always have rights that Administrators have.
       </p>
     </section3>
 
@@ -536,7 +538,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
     </section3>
 
     <section3 topic="Participants Node" anchor="participants-node">
-      <p>Each channel participant is represented as an item of the 'urn:xmpp:mix:nodes:participants' channel node.  Each item is named by the bare proxy JID of the participant. For example '123456#coven@mix.shakespeare.example' might name the node item associated with participant 'hag66@shakespeare.example'.  Information is stored in a &lt;participant/&gt; element qualified by the 'urn:xmpp:mix:1' namespace.   The nick associated with the user is mandatory and is stored in a &lt;nick/&gt; child element of the &lt;participant/&gt; element.   The nick for each channel participant MUST be different to the nick of other participants.
+      <p>Each channel participant is represented as an item of the 'urn:xmpp:mix:nodes:participants' channel node.  Each item is named by the bare proxy JID of the participant. For example '123456#coven@mix.shakespeare.example' might name the node item associated with participant 'hag66@shakespeare.example'.  Information is stored in a &lt;participant/&gt; element qualified by the 'urn:xmpp:mix:1' namespace.   The nick associated with the user is optional and is stored in a &lt;nick/&gt; child element of the &lt;participant/&gt; element.   The nick for each channel participant MUST be different to the nick of other participants.
       </p>
       <p>
         When a user joins a channel, the user's bare proxy JID is added to the participants node by the MIX service.   When a user leaves a channel, the user's bare proxy JID is removed from the participants node.  The participants node MUST NOT be directly modified using pubsub.