From 19c32fce88eefccbe461e789be55c08afb8b94cb Mon Sep 17 00:00:00 2001
From: Sam Whited <sam@samwhited.com>
Date: Wed, 6 May 2020 09:02:30 -0400
Subject: [PATCH] XEP-0389: inline examples in Retrieving the Flows

---
 xep-0389.xml | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/xep-0389.xml b/xep-0389.xml
index 502eb949..2f0980fe 100644
--- a/xep-0389.xml
+++ b/xep-0389.xml
@@ -293,19 +293,17 @@
       &lt;register&gt; or &lt;recovery&gt; element qualified by the
       "urn:xmpp:register:0" namespace.
     </p>
+    <example caption='Registration flows query'><![CDATA[
+<iq type='get'>
+  <register xmlns='urn:xmpp:register:0'/>
+</iq>]]></example>
     <p>
       When responding to a query for registration or recovery flows the list of
       challenges should be included just as it would be if during stream feature
       negotiation.
       That is, a "register" or "recovery" element containing a list of flows,
       each with an id, containing a name and a list of challenges.
-      If an entity supports this specification but does not provide any flows
-      after stream negotiation it MUST respond with an empty list.
     </p>
-    <example caption='Registration flows query'><![CDATA[
-<iq type='get'>
-  <register xmlns='urn:xmpp:register:0'/>
-</iq>]]></example>
     <example caption='Registration flows results'><![CDATA[
 <iq type='result'>
   <register xmlns='urn:xmpp:register:0'>
@@ -324,6 +322,10 @@
     </flow>
   </register>
 </iq>]]></example>
+    <p>
+      If an entity supports this specification but does not provide any flows
+      after stream negotiation it MUST respond with an empty list.
+    </p>
     <example caption='Empty registration flows results'><![CDATA[
 <iq type='result'>
   <register xmlns='urn:xmpp:register:0'/>