Note on MAM history prior to user joining channel

xep-0369.xml

@@ -1420,6 +1420,9 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
         <li>The client MAY wish to display messages from a recent time period, perhaps finding more messages if the user subsequently requests.</li>
       </ol>
       <p>To achieve this, the client will query the user's own MAM archive using &xep0313;, with the query filtered by the channel JID.   This gives the client flexibility to retrieve and display message history in a manner appropriate to the client implementation.</p>
+      <p>
+        The only exception to this is when a user wishes to access message history in the channel prior to when the user joined the channel.  To achieve this, the client will use MAM to retrieve message history directly from the MAM Archive of the MUX channel.
+      </p>
     </section3>
 
 
@@ -2236,7 +2239,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
 
   <section2 topic="MIX Management and Discovery" anchor="user-server-disco">
     <p>
-      Most interaction between  a MIX client and a MIX channel is directly between the client and the channel channel. The participant's server relays the message but does not modify the messages.   In particular configuration management and discovery is direct.   Interaction will be direct, unless explicitly stated otherwise.
+      Most interaction between  a MIX client and a MIX channel is directly between the client and the channel. The participant's server relays the message but does not modify the messages.   In particular configuration management and discovery is direct.   Interaction will be direct, unless explicitly stated otherwise.
     </p>
   </section2>
   <section2 topic="IQ Support on Local Server" anchor="mix-diso">