From 15f08a79472a89ccd972856efc7422ac67506258 Mon Sep 17 00:00:00 2001
From: Steve Kille <steve.kille@isode.com>
Date: Fri, 16 Jun 2017 07:08:31 +0100
Subject: [PATCH] mick-register rename

---
 xep-0369.xml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/xep-0369.xml b/xep-0369.xml
index c3d5e290..233943cb 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -38,7 +38,7 @@
   &stpeter;
   <revision>
     <version>0.9.3</version>
-    <date>2017-06-15</date>
+    <date>2017-06-16</date>
     <initials>sek</initials>
     <remark><p>
       Remove Legacy MIX Namespace;
@@ -47,6 +47,7 @@
       Clarify when messages are delivered to clients;
       Extend Roster Get to select format;
       Ensure that text defining attributes and elements reference the namespace;
+      Change mix_nick_register to nick-register;
     </p></remark>
   </revision>
   <revision>
@@ -1403,12 +1404,12 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
     from='mix.shakespeare.example'
     id='7nve413p'>
     <query xmlns='http://jabber.org/protocol/disco#info'/>
-        <feature var='urn:xmpp:mix:0#mix_nick_register'/>
+        <feature var='urn:xmpp:mix:0#nick-register'/>
     </query>
 </iq>
 ]]></example>
       <p>
-        The response will be a list of features of the MIX channel.  If Nick Registration is supported, then the result set will include &lt;feature var="urn:xmpp:mix:0#mix_nick_register"/&gt;.
+        The response will be a list of features of the MIX channel.  If Nick Registration is supported, then the result set will include &lt;feature var="urn:xmpp:mix:0#nick-register"/&gt;.
       </p>
       <p>
         To register a nick with the MIX service the user sends