From 08a9372ba6d442c87c88b446c719846ea47f4c46 Mon Sep 17 00:00:00 2001
From: 6k27f <6k27f@localhost>
Date: Wed, 5 Jan 2022 00:00:00 +0000
Subject: [PATCH 1/2] Fix broken links.

The actual anchor in the Business Rules section is rules.
---
 xep-0384.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xep-0384.xml b/xep-0384.xml
index 436340d1..e2f1f6e7 100644
--- a/xep-0384.xml
+++ b/xep-0384.xml
@@ -594,8 +594,8 @@
   </section2>
   <section2 topic='Receiving a message' anchor='usecases-receiving'>
     <p>When an OMEMO element is received, the client MUST check whether there is a &lt;keys&gt; element with a jid attribute matching its own bare jid and an inner &lt;key&gt; element with a rid attribute matching its own device id. If this is not the case the message was not encrypted for this particular device and a warning message SHOULD be displayed instead. If such an element exists, the client checks whether the element's contents are an OMEMOKeyExchange.</p>
-    <p>If this is the case, a new session is built from this received element. The client MUST then republish their bundle information, replacing the used PreKey, such that it won't be used again by a different client. If the client already has a session with the sender's device, it MUST replace this session with the newly built session. The client MUST eventually delete the private key belonging to the PreKey after use (this is subject to the <link url='#business-rules'>Business rules</link>).</p>
-    <p>If the element's contents are an OMEMOAuthenticatedMessage, and the client has a session with the sender's device, it tries to decrypt the OMEMOAuthenticatedMessage using this session. If the decryption fails or there is no session with the sending device, a warning message SHOULD be displayed instead. Also refer to the section about recovering from broken sessions in the <link url='#business-rules'>Business Rules</link>.</p>
+    <p>If this is the case, a new session is built from this received element. The client MUST then republish their bundle information, replacing the used PreKey, such that it won't be used again by a different client. If the client already has a session with the sender's device, it MUST replace this session with the newly built session. The client MUST eventually delete the private key belonging to the PreKey after use (this is subject to the <link url='#rules'>Business rules</link>).</p>
+    <p>If the element's contents are an OMEMOAuthenticatedMessage, and the client has a session with the sender's device, it tries to decrypt the OMEMOAuthenticatedMessage using this session. If the decryption fails or there is no session with the sending device, a warning message SHOULD be displayed instead. Also refer to the section about recovering from broken sessions in the <link url='#rules'>Business Rules</link>.</p>
     <p>
       After either the OMEMOKeyExchange or the OMEMOAuthenticatedMessage is decrypted, the content is decrypted as described in the section about <link url='#protocol-message_decryption'>Message Decryption</link>.
     </p>

From 5774e9d3aa3fe949cc267246689c163015fa1686 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= <j.wielicki@sotecware.net>
Date: Tue, 18 Jan 2022 15:53:05 +0100
Subject: [PATCH 2/2] XEP-0384: add revision block

---
 xep-0384.xml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/xep-0384.xml b/xep-0384.xml
index e2f1f6e7..c1868c40 100644
--- a/xep-0384.xml
+++ b/xep-0384.xml
@@ -57,6 +57,14 @@
     <email>xmpp@larma.de</email>
     <jid>jabber@larma.de</jid>
   </author>
+  <revision>
+    <version>0.8.3</version>
+    <date>2022-01-18</date>
+    <initials>gh/@6k27f</initials>
+    <remark>
+      <p>Fix broken links</p>
+    </remark>
+  </revision>
   <revision>
     <version>0.8.2</version>
     <date>2021-12-27</date>