--- a/paq/prov-aq.html	Thu Apr 11 13:27:31 2013 -0400
+++ b/paq/prov-aq.html	Fri Apr 12 11:31:32 2013 +0100
@@ -1001,20 +1001,20 @@
         For example, consider a resource that is published by <code>acme.example.com</code>, and is subsequently used by <code>coyote.example.org</code> in the construction of some new entity;  we might see an exchange along the following lines.  We start with <code>coyote.example.org</code> retrieving a copy of <code>acme.example.org</code>'s resource:
       </p>
       <pre class="example code">
-  C: GET http://acme.example.org/super-widget HTTP/1.1
+  C: GET http://acme.example.org/super-widget123 HTTP/1.1
 
   S: 200 OK
-  S: Link: &lt;http://acme.example.org/super-widget/provenance&gt;; 
+  S: Link: &lt;http://acme.example.org/super-widget123/provenance&gt;; 
            rel="http://www.w3.org/ns/prov#has_provenance"
-  S: Link: &lt;http://acme.example.org/super-widget/pingback&gt;; 
+  S: Link: &lt;http://acme.example.org/super-widget123/pingback&gt;; 
            rel="http://www.w3.org/ns/prov#pingback"
    :
-  (super-widget resource data)</pre>
+  (super-widget123 resource data)</pre>
       <p>
-        The first of the links in the response is a <code>has_provenance</code> link with a <a class="internalDFN">provenance-URI</a> that has been described previously (<a href="#resource-accessed-by-http" class="sectionRef"></a>).  The second is a distinct resource that exists to receive provenance pingbacks.  Later, when a new resource has been created or some related action performed based upon the <code>acme.example.org/super-widget</code>, a client may post a pingback request to any supplied <code>pingback</code> URI:
+        The first of the links in the response is a <code>has_provenance</code> link with a <a class="internalDFN">provenance-URI</a> that has been described previously (<a href="#resource-accessed-by-http" class="sectionRef"></a>).  The second is a distinct resource that exists to receive provenance pingbacks.  Later, when a new resource has been created or some related action performed based upon the <code>acme.example.org/super-widget123</code>, a client may post a pingback request to the supplied <code>pingback</code> URI:
       </p>
       <pre class="example code">
-  C: POST http://acme.example.org/super-widget/pingback HTTP/1.1
+  C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
   C: Content-Type: text/uri-list
   C:
   C: http://coyote.example.org/contraption/provenance
@@ -1036,7 +1036,7 @@
         The pingback client MAY include extra <code>has_provenance</code> links to indicate provenance records related to a different resources, specified with correspondingly different anchor URIs. For example:
       </p>
       <pre class="example code">
-  C: POST http://acme.example.org/super-widget/pingback HTTP/1.1
+  C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
   C: Link: &lt;http://coyote.example.org/extra/provenance&gt;;
            rel="http://www.w3.org/ns/prov#has_provenance";
            anchor="http://acme.example.org/extra-widget"
@@ -1049,13 +1049,13 @@
   S: 204 No Content
 </pre>
       <p>
-        The client MAY also supply <code>has_query_service</code> links indicating provenance query services that can describe the target-URI. The anchor MUST be included, and SHOULD be either the target-URI of the resource for which the pingback URI was provided (from the examples above, that would be <code>http://acme.example.org/super-widget</code>), or some related resource with relevant provenance.  For example:
+        The client MAY also supply <code>has_query_service</code> links indicating provenance query services that can describe the target-URI. The anchor MUST be included, and SHOULD be either the target-URI of the resource for which the pingback URI was provided (from the examples above, that would be <code>http://acme.example.org/super-widget123</code>), or some related resource with relevant provenance.  For example:
       </p>
       <pre class="example code">
-  C: POST http://acme.example.org/super-widget/pingback HTTP/1.1
+  C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
   C: Link: &lt;http://coyote.example.org/sparql&gt;;
            rel="http://www.w3.org/ns/prov#has_query_service";
-           anchor="http://acme.example.org/super-widget"
+           anchor="http://acme.example.org/super-widget123"
   C: Content-Type: text/uri-list
   C: Content-Length: 0
   C:
@@ -1063,7 +1063,7 @@
   S: 204 No Content
 </pre>
       <p>
-        Here, the pingback client has supplied a query service URI, but did not submit any provenance-URIs and the URI list is therefore empty.  The <code>Link</code> header field indicates that the resource <code>http://acme.example.org/super-widget/provenance</code> contains provenance information relating to <code>http://acme.example.org/super-widget</code> (that being the URI of the resource for which the pingback URI was provided).
+        Here, the pingback client has supplied a query service URI, but did not submit any provenance-URIs and the URI list is therefore empty.  The <code>Link</code> header field indicates that the resource <code>http://acme.example.org/super-widget123/provenance</code> contains provenance information relating to <code>http://acme.example.org/super-widget123</code> (that being the URI of the resource for which the pingback URI was provided).
       </p>
 
       <!-- also in Stian's proposal