From 56255283cf6ee081e029b106937e94fc9e6aec50 Mon Sep 17 00:00:00 2001
From: Steve Kille <steve.kille@isode.com>
Date: Tue, 2 Jan 2018 10:07:14 +0000
Subject: [PATCH] Correct JID description in client going offline presence
 share.

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

diff --git a/xep-0369.xml b/xep-0369.xml
index af76f65d..160bc984 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -46,6 +46,7 @@
       Participant's Node Joining clarification,
       Joining Channel Clarification, 
       Coming online clarification,
+      Going offline JID error,
       
     </p></remark>
   </revision>  <revision>
@@ -1661,7 +1662,8 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
           from='hag66@shakespeare.example/UUID-a1j/7533'
           to='coven@mix.shakespeare.example'/>
 ]]></example>
-      <p>The MIX channel will retract (remove) the item in the presence node of the MIX channel identified by the client's full JID.  The MIX channel will notify subscribers to the presence node of the user going offline by sending a presence stanza to the full proxy JID of each client.</p>
+      <p>The MIX channel will retract (remove) the item in the presence node of the MIX channel identified by the client's full JID.  The MIX channel will notify subscribers to the presence node of the user going offline by sending a presence stanza to the full  JID of each client. The presence stanza will reference the full proxy JID of the client that is going offline, as shown in the following example:</p>
+      
       <example caption="Channel Distributes Notification of Client going Offline">
 <![CDATA[<presence from='12345#coven@mix.shakespeare.example/678'
           to='hecate@shakespeare.example'