QUERY: examples - split sections for C-L and L, and add fwd pointers to examples (see #3114)

Author: reschke

draft-ietf-httpbis-safe-method-w-body.xml

@@ -253,7 +253,7 @@ q=foo&limit=10&sort=-published
       it is expected to describe the results of the operation.
     </t>
 
-    <section title="Content-Location and Location Fields" anchor="location">
+    <section title="Content-Location Response Field" anchor="content-location">
       <t>
         A successful response (2xx, <xref target="HTTP" section="15.3"/>)
         can include a Content-Location
@@ -263,6 +263,12 @@ q=foo&amp;limit=10&amp;sort=-published
         a GET request for the indicated URI to retrieve the results of the query
         operation just performed. The indicated resource might be temporary.
       </t>
+      <t>
+        See <xref target="example.content-location"/> for an example.
+      </t>
+    </section>
+
+    <section title="Location Response Field" anchor="location">
       <t>
         A server can create or locate a resource that identifies the query
         operation for future use. If the server does so, the URI of the resource
@@ -273,6 +279,9 @@ q=foo&amp;limit=10&amp;sort=-published
         temporary; if a future request fails, the client can retry using the
         original QUERY resource and the previously submitted content.
       </t>
+      <t>
+        See <xref target="example.location"/> for an example.
+      </t>
     </section>
 
     <section title="Redirection" anchor="redirection">
@@ -659,7 +668,8 @@ Accept: application/x-www-form-urlencoded, application/sql
 
     <section title="Content-Location, Location, and Indirect Responses" anchor="example.content-location.location.indirect">
       <t>
-        As described in <xref target="location"/>, the Content-Location and Location response fields in success responses
+        As described in Sections <xref format="counter" target="content-location"/> and
+        <xref format="counter" target="location"/>, the Content-Location and Location response fields in success responses
         (2xx, <xref target="HTTP" section="15.3"/>) provide a way to identify alternate resources
         that will respond to GET requests, either for the received result of the request, or for future
         requests to perform the same operation. Going back to the example from <xref target="example.simple"/>: