From f1d2442f05bd1270f57f0963c837211bda9a9c76 Mon Sep 17 00:00:00 2001
From: Manuel Rubio <manuel.rubio@veon.com>
Date: Mon, 12 Mar 2018 16:03:53 +0100
Subject: [PATCH] fix typo error (XEP-0369)

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

diff --git a/xep-0369.xml b/xep-0369.xml
index 04876db3..99bef508 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -1314,7 +1314,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
     to='hag66@shakespeare.example'
     id='E6E10350-76CF-40C6-B91B-1EA08C332FC7'>
   <leave xmlns='urn:xmpp:mix:1'
-          channel=`coven@mix.shakespeare.example`/>
+          channel='coven@mix.shakespeare.example`/>
 </iq>
 ]]></example>
 
@@ -1514,7 +1514,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
       <p>
         A user setting status is now used as an example.   Unlike in &xep0045; where coming online is a special action, coming online in MIX is implicit when presence status is set.  Going offline is a achieved by setting presence status to unavailable, which removes the client full JID entry from the presence node.  When a user sets a presence status, the user's server sends updated presence to the MIX channel, and the MIX service then publishes the user's  availability to the "urn:xmpp:mix:nodes:presence" node. If there is not an item named by the full JID of the client with updated presence status, this item is created.   The sequence is shown in the following examples, starting with a client setting presences status on the connected server.</p>
       <example caption="Client Sets Presence Status on Server">
-        <![CDATA[<presence xmlns='jabber:client' from=‘hag66@shakespeare.example/UUID-a1j/7533’>
+        <![CDATA[<presence xmlns='jabber:client' from='hag66@shakespeare.example/UUID-a1j/7533'>
   <show>dnd</show>
   <status>Making a Brew</status>
 </presence>]]></example>
@@ -1523,7 +1523,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
         The server then sends the presence information to roster entries.  The following example then shows the presence message from the client's server to the MIX channel.
       </p>
       <example caption="Server sends Presence Status to MIX Channel">
-<![CDATA[<presence  from=‘hag66@shakespeare.example/UUID-a1j/7533’
+<![CDATA[<presence  from='hag66@shakespeare.example/UUID-a1j/7533'
               to='coven@mix.shakespeare.example'>
   <show>dnd</show>
   <status>Making a Brew</status>
@@ -2252,7 +2252,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
         <field type='text-multi'
                label='Channel Description'
                var='Description'/>
-         <field type=jid-single'
+         <field type='jid-single'
                 label='Channel Administrative Contact'
                 var='Contact'/>
       </x>
@@ -2323,7 +2323,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
              <value>urn:xmpp:mix:1</value>
         </field>
         <title>Configuration Node Modification</title>
-         <field type=jid-multi'
+         <field type='jid-multi'
                 label='Channel Administrator'
                 var='Administrator'/>
       </x>
@@ -2617,7 +2617,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
           id='bv1bs71f'
           type='get'>
        <query xmlns='jabber:iq:roster'>
-              <annotate xmlns=‘urn:xmpp:mix:roster:0'/>
+              <annotate xmlns='urn:xmpp:mix:roster:0'/>
        <query/>
      </iq>
 ]]></example>
@@ -2633,7 +2633,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
 
     <example caption="Roster Item Encoding of a MIX Channel"><![CDATA[
   <item jid='balcony@example.net'>
-      <channel xmlns=‘urn:xmpp:mix:roster:0'/>
+      <channel xmlns='urn:xmpp:mix:roster:0'/>
   </item>
 ]]></example>