Switch order based on feedback.

Author: handrews

jsonschema-hyperschema.xml

@@ -395,14 +395,6 @@
                         hint may be added in a future draft (see issue #73 in the GitHub repository).
                     </cref>
                 </t>
-                <t>
-                    Link Description Objects do not directly indicate what operations, such
-                    as HTTP methods, are supported by the target resource.  Instead, operations
-                    should be inferred primarily from link <xref target="rel">relation types</xref>
-                    and URI schemes.  Note, however, that a resource may always decline an operation at
-                    runtime, for instance due to application state that controls the operation's
-                    availability.
-                </t>
                 <t>
                     There are several ways that a client can use data can with a link:
                     <list>
@@ -416,6 +408,14 @@
                     schema keyword within the link description object.  Link operations
                     ignore schemas that are not relevant to their semantics.
                 </t>
+                <t>
+                    Link Description Objects do not directly indicate what operations, such
+                    as HTTP methods, are supported by the target resource.  Instead, operations
+                    should be inferred primarily from link <xref target="rel">relation types</xref>
+                    and URI schemes.  Note, however, that a resource may always decline an operation at
+                    runtime, for instance due to application state that controls the operation's
+                    availability.
+                </t>
                 <section title="Resolving templated URIs">
                     <t>
                         URI Template variables in <xref target="href">"href"</xref> resolve from