From 69234eea1513a4399ce25185d4f5de7938381a58 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Tue, 5 Jun 2018 13:01:40 +0100 Subject: [PATCH] editorial --- xep-0369.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xep-0369.xml b/xep-0369.xml index 6d018030..ecbad6ce 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -412,7 +412,7 @@
  • XMPP clients can implement MUC and this specification in a way that provides a coherent user experience.
  • XMPP servers can implement this specification and also provide a MUC interface in order to support clients that only implement MUC.
    • -

    This specification gives guidance on supporting both MUC and MIX representations of chatrooms.

    +

    MIX gives guidance on supporting both MUC and MIX representations of chatrooms.

    @@ -1161,7 +1161,7 @@ Harpier cries: 'tis time, 'tis time. thirdwitch - 123456#coven@mix.shakespeare.example + hag66@shakespeare.example ]]> @@ -1184,7 +1184,7 @@ The messages sent to participants have a different message id to the originally submitted message. This does not impact most recipients, but it does not allow the message originator to correlate the message with the submitted message. To address this the MIX channel MUST include an additional <submission-id> element in the <mix> element of the message copy going back to the originator's bare JID. The <submission-id> element holds the original id provided by the sender. This enables the originator to correlate the received message with the message submitted.