--- a/paq/releases/WD-prov-aq-20120619/prov-aq.html	Wed Jun 13 14:54:31 2012 -0500
+++ b/paq/releases/WD-prov-aq-20120619/prov-aq.html	Wed Jun 13 14:56:36 2012 -0500
@@ -516,11 +516,11 @@
 
      <section>
         <h2>HTTP GET</h2>
-        <p>This protocol combines the <a class="internalDFN">target-URI</a> with the <a class="internalDFN">service-URI</a> to formulate an HTTP GET request, according to the following convention:
+        <div>This protocol combines the <a class="internalDFN">target-URI</a> with the <a class="internalDFN">service-URI</a> to formulate an HTTP GET request, according to the following convention:
           <pre class="pattern">
   GET /provenance/service?<b>target</b>=http://www.example.com/entity HTTP/1.1
   Host: example.com</pre>
-        </p>
+        </div>
         <div>The embedded target-URI (<code>http://www.example.com/entity</code>) identifies the resource for which provenance information is to be returned. Any server that implements this protocol and receives a request URI in this form SHOULD return provenance information for the resource-URI embedded in the query component where that URI is the result of percent-decoding the value associated with the provenance-resource key. The embedded URI MUST be an absolute URI and the server MUST respond with a 400 Bad Request if it is not.  If the supplied resource-URI includes a fragment identifier, the '#' MUST be %-encoded as <code>%23</code> when constructing the provenance-URI value; similarly, any '&amp;' character in the resource-URI must be %-encoded as <code>%26</code>.
         </div>
         <p>If the provenance information identified in the request does not exist in the server, a 404 Not Found response code SHOULD be returned.
@@ -573,14 +573,14 @@
       <section id="querying-provenance-information">
         <h2>Using SPARQL for provenance queries</h2>
         <p>
-          Simply identifying and retrieving provenance information as a resource on the Web may not always meet the requirements of a particular application or service, e.g.:
+          Simply identifying and retrieving provenance information as a resource on the Web may not always meet the requirements of a particular application or service, e.g.:</p>
           <ul>
             <li>the resource for which provenance information is required is not identified by a known URI</li>
             <li>the provenance information for a resource is not directly identified by a known URI</li>
             <li>a requirement to access provenance information for a number of distinct but related resources in a single atomic operation</li>
             <li><i>etc.</i></li>
           </ul>
-        </p>
+   
         <p>
           A provenance query service provides an alternative way to access provenance information and/or provenance-URIs.  An application will need a URI for the provenance query service, and some relevant information about the resource whose provenance is to be accessed.
         </p>
@@ -599,15 +599,15 @@
         <section>
           <h2>Find a provenance-URI given a target-URI</h2>
           <p>
-            If the requester has a <a class="internalDFN">target-URI</a>, a simple SPARQL query may be used to return the corresponding <a class="internalDFN">provenance-URI</a>. E.g., if the original resource has a target-URI <code>http://example.org/resource</code>:
+            If the requester has a <a class="internalDFN">target-URI</a>, a simple SPARQL query may be used to return the corresponding <a class="internalDFN">provenance-URI</a>. E.g., if the original resource has a target-URI <code>http://example.org/resource</code>:</p>
             <pre class="example code">
-  @prefix prov: &lt;<provns/>&gt;
+  @prefix prov: &lt;http://www.w3c.org/ns/prov#&gt;
   SELECT ?provenance_uri WHERE
   {
     &lt;http://example.org/resource&gt; prov:hasProvenance ?provenance_uri
   }
             </pre>
-          </p>
+       
         </section>
 
         <section>