From 76b358907abc5c54252c73acbb6a6f8039e385be Mon Sep 17 00:00:00 2001 From: JC Brand Date: Mon, 26 Oct 2015 07:01:20 +0000 Subject: [PATCH] Fix typo ("cannot" repeated twice). --- xep-0333.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/xep-0333.xml b/xep-0333.xml index 9ef737cb..77d851dc 100644 --- a/xep-0333.xml +++ b/xep-0333.xml @@ -10,7 +10,7 @@ This specification describes a solution of marking the last received, displayed and acknowledged message in a chat. &LEGALNOTICE; 0333 - Deferred + Experimental Standards Track Standards Council @@ -27,6 +27,12 @@ im@spencermacdonald.com im@spencermacdonald.com + + 0.2.1 + 2015-10-28 + XEP Editor (mam) +

Fixing typo ("cannot" repeated twice) (JC Brand).

+
0.2 2013-09-05 @@ -133,7 +139,7 @@ -

If the sender knows only the recipient's bare JID, it cannot cannot determine (via &xep0030; or &xep0115;) whether the intended recipient supports the Chat Markers protocol. In this case, the sender MAY send a Chat Marker or markable message.

+

If the sender knows only the recipient's bare JID, it cannot determine (via &xep0030; or &xep0115;) whether the intended recipient supports the Chat Markers protocol. In this case, the sender MAY send a Chat Marker or markable message.

If the sender knows a full JID for the recipient (e.g., via presence), it SHOULD attempt to determine (via service disco or entity capabilities) whether the client at that full JID supports the Chat Markers protocol before attempting to send a Chat Marker or markable message.