diff --git a/xep-0369.xml b/xep-0369.xml
index ad02ab27..39f2835b 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -42,6 +42,7 @@
     <remark><p>
       Remove Proxy JID;
       Add Stable Participant ID;
+      Remove reommendation to generate Nick as UUID;
     </p></remark>
   </revision>  <revision>
     <version>0.11.3</version>
@@ -1081,7 +1082,7 @@
       <li>The nick is registered with the user account in some way, for example as part of user provisioning with nick configured as an attribute in a directory service.   For example, this could be chosen by corporate services that wish to ensure consistent nick values for a set of users and channels.</li>
       <li>The nick is registered with the MIX service, as described in  <link url='#usecase-user-register'> Registering a Nick </link>.</li>
       <li>The user explicitly sets the nick, as described in this section.</li>
-      <li>The MIX service generates the nick.  In this case it is RECOMMENDED that the assigned nick is a UUID following &rfc4122;.</li>
+      <li>The MIX service generates the nick.  </li>
     </ol>
     <p>
       A user will typically set a nick when joining a channel and MAY update this nick from time to time.   The user does this by sending a command to the channel to set the nick.  This command is a &lt;setnick/&gt; child element of &lt;iq/&gt; element. The &lt;setnick/&gt; element is qualified by the 'urn:xmpp:mix:core:0' namespace.   The nick is encoded as a &lt;nick/&gt; child element of the &lt;setnick/&gt; element. If the user wishes the channel to assign a nick (or knows that the channel will assign a nick) the nick field can be left blank, so that the user can see what is assigned in the result.