moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 15:18:51 -05:00
Code Issues Releases Wiki Activity

Fix typos. "Chat Maker" should be "Chat Marker"

Browse Source
This commit is contained in:
JC Brand 2019-02-01 11:31:14 +01:00
parent e265f78979
commit 731442bf8a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0333.xml
View File

@ -156,7 +156,7 @@
<p>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.</p>
</section2>
<section2 topic='Chat Marker' anchor='when-chat-marker'>
<p>To prevent looping, an entity MUST NOT send a Chat Maker to mark up to a Chat Marker.</p>
<p>To prevent looping, an entity MUST NOT send a Chat Marker to mark up to a Chat Marker.</p>
</section2>
</section1>
@ -211,7 +211,7 @@
<p>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.</p>
<p>Messages MUST have an 'id' to use Chat Markers.</p>
<p>Messages MUST include the 'markable' element to use Chat Markers.</p>
<p>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.
<p>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.
</p>
<p>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.
</p>