From 3cccbf5c00fb77d3b8a8c72274551df434e631e1 Mon Sep 17 00:00:00 2001
From: Georg Lukas <georg@op-co.de>
Date: Thu, 16 Feb 2017 10:42:27 +0100
Subject: [PATCH] XEP-0379: moved UX sections to 'Usability Considerations'

---
 xep-0379.xml | 41 +++++++++++++++++++++--------------------
 1 file changed, 21 insertions(+), 20 deletions(-)

diff --git a/xep-0379.xml b/xep-0379.xml
index 35a9b849..b5067cf0 100644
--- a/xep-0379.xml
+++ b/xep-0379.xml
@@ -266,26 +266,6 @@ https://juicyxmpp.example/i/#romeo@montague.net?preauth=1tMFqYDdKhfe2pwp;name=Ro
         same mechanism as before to indicate an unidirectional subscription.
       </p>
     </section2>
-
-    <section2 topic='Use of multiple clients' anchor='rules_multiclient'>
-      <p>If a user is logged in with multiple clients, some of their clients will
-        receive a subscription request with an unknown token. In this case, a client
-        MAY delay the user notification for a short time, to allow another logged-in
-        client to automatically handle the subscription request.</p>
-    </section2>
-
-    <section2 topic='Opening the landing page in an app' anchor='rules_multiclient'>
-      <p>Some mobile device platforms allow an app to register itself as a
-        handler for cetain URIs. This allows an XMPP client to register for <strong>xmpp:</strong>
-        URIs, but also to redirect handling of cetain HTTP/HTTPS URIs. A mobile
-        client SHOULD register for the associated landing page URIs and properly
-        handle the contained invitations. For example, the JuicyXMPP client should
-        register a handler for <strong>https://juicyxmpp.example/i/*</strong>, and present
-        the "Add to roster" dialog if such a link is opened. A client MAY register
-        for the landing page URIs of other providers after obtaining the
-        operators' approval.
-      </p>
-    </section2>
   </section1>
   <section1 topic='Security Considerations' anchor='security'>
     <section2 topic='Token Generation' anchor='security_token'>
@@ -352,6 +332,27 @@ https://juicyxmpp.example/i/#romeo@montague.net?preauth=1tMFqYDdKhfe2pwp;name=Ro
         equal to the JID, to prevent impersonation attacks.</p>
     </section2>
   </section1>
+  <section1 topic='Usability Considerations' anchor='usability'>
+    <section2 topic='Use of multiple clients' anchor='rules_multiclient'>
+      <p>If a user is logged in with multiple clients, some of their clients will
+        receive a subscription request with an unknown token. In this case, a client
+        MAY delay the user notification for a short time, to allow another logged-in
+        client to automatically handle the subscription request.</p>
+    </section2>
+
+    <section2 topic='Opening the landing page in an app' anchor='rules_multiclient'>
+      <p>Some mobile device platforms allow an app to register itself as a
+        handler for cetain URIs. This allows an XMPP client to register for <strong>xmpp:</strong>
+        URIs, but also to redirect handling of cetain HTTP/HTTPS URIs. A mobile
+        client SHOULD register for the associated landing page URIs and properly
+        handle the contained invitations. For example, the JuicyXMPP client should
+        register a handler for <strong>https://juicyxmpp.example/i/*</strong>, and present
+        the "Add to roster" dialog if such a link is opened. A client MAY register
+        for the landing page URIs of other providers after obtaining the
+        operators' approval.
+      </p>
+    </section2>
+  </section1>
   <section1 topic='IANA Considerations' anchor='iana'>
     <p>This document requires no interaction with &IANA;.</p>
   </section1>