From 731442bf8a254a280a6b6d7e76b7aa32de74a16b Mon Sep 17 00:00:00 2001 From: JC Brand Date: Fri, 1 Feb 2019 11:31:14 +0100 Subject: [PATCH] Fix typos. "Chat Maker" should be "Chat Marker" --- xep-0333.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0333.xml b/xep-0333.xml index 31c31db6..86582e12 100644 --- a/xep-0333.xml +++ b/xep-0333.xml @@ -156,7 +156,7 @@

If the sender determines that the recipient's client supports the Chat Markers protocol then it MAY send a Chat Marker or markable message to that full JID.

-

To prevent looping, an entity MUST NOT send a Chat Maker to mark up to a Chat Marker.

+

To prevent looping, an entity MUST NOT send a Chat Marker to mark up to a Chat Marker.

@@ -211,7 +211,7 @@

Clients SHOULD use &xep0136; or &xep0313; to support offline updating of Chat Markers. Chat Markers SHOULD be archived, so they can be fetched and set regardless of whether the other users in a chat are online.

Messages MUST have an 'id' to use Chat Markers.

Messages MUST include the 'markable' element to use Chat Markers.

-

Chat Markers MUST only move forward. If a Chat Maker is received for an earlier message than the current Chat Marker, it MUST be ignored by the client. +

Chat Markers MUST only move forward. If a Chat Marker is received for an earlier message than the current Chat Marker, it MUST be ignored by the client.

Chat Markers for unknown messages MUST be ignored by the client. A client MAY store the Chat Marker incase the associated message is retrieved later.