diff --git a/xep-0404.xml b/xep-0404.xml
index 09085aad..66ed92cf 100644
--- a/xep-0404.xml
+++ b/xep-0404.xml
@@ -119,13 +119,13 @@ Private messages MAY be switched through the channel when JIDs are visible.  Thi
 
     <section2 topic="JID Visibility Architecture" anchor="proxy-jid-architecture">
       <p>
-         MUC hides real JIDs by using Nicks to identify room occupants.  This has problems with Nick changing and with multiple active clients for the same user.    MIX identifies channel participants by Stable Participant ID.  In &xep0369;, the users JID is in the participants node and is shared in messages and presence.    To hide JIDs, this specification makes three key changes
+         MUC hides real JIDs by using Nicks to identify room occupants.  This has problems with Nick changing and with multiple active clients for the same user.    MIX identifies channel participants by Stable Participant ID.  In &xep0369;, the user's JID is in the participants node and is shared in messages and presence.    To hide JIDs, this specification makes three key changes
 
       </p>
 
       <ol>
         <li>The requirement to include real JID in the participants list is relaxed for channels that are not "JID Visible".  For a "JID Hidden" channel, real JIDs MUST NOT be included in the participants list.    For a "JID Maybe Visible" channel, real JIDs will be included in the participants node according to participant preference. </li>
-        <li>JIDs are not shared in messages and presence.</li>
+        <li>JIDs are not shared in messages and presence, unless the recipient has permission to see the JID.  Note that in JID Maybe Visible channels, this leads to the creation of two variants of message and presence.   The MAM archive MUST hold only the variant without the JID, in order to prevent leaking of this information.</li>
         <li>In presence messages, the client resource is anonymized, to prevent leakage of information through the resource.</li>
       </ol>
 
@@ -136,7 +136,7 @@ This change means that the client will not be able to determine real JID of the
       </p>
 
       <p>
-        It is important that MUC owners and administrators are able to see the  JIDs of participant.   For this reason, a MIX channel following this specification MUST hold a JID Map node, which gives a mapping between Stable Participant ID and  JID.
+        It is important that MUC owners and administrators are able to see the  JIDs of participants.   For this reason, a MIX channel following this specification MUST hold a JID Map node, which gives a mapping between Stable Participant ID and  JID.
       </p>