--- a/paq/releases/WD-prov-aq-20120619/prov-aq.html	Wed Jun 13 14:56:36 2012 -0500
+++ b/paq/releases/WD-prov-aq-20120619/prov-aq.html	Wed Jun 13 14:59:32 2012 -0500
@@ -601,7 +601,7 @@
           <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>:</p>
             <pre class="example code">
-  @prefix prov: &lt;http://www.w3c.org/ns/prov#&gt;
+  @prefix prov: &lt;http://www.w3.org/ns/prov#&gt;
   SELECT ?provenance_uri WHERE
   {
     &lt;http://example.org/resource&gt; prov:hasProvenance ?provenance_uri
@@ -613,16 +613,16 @@
         <section>
           <h2>Find Provenance-URI given identifying information about a resource</h2>
           <p>
-            If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate a resource description and obtain its provenance-URI(s).  The nature of identifying information that can be used in this way will depend upon the third party service used, further definition of which is out of scope for this specification.  For example, a query for a document identified by a DOI, say <code>1234.5678</code>, using the PRISM vocabulary [[PRISM]] recommended by FaBio [[FABIO]], might look like this:
+            If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate a resource description and obtain its provenance-URI(s).  The nature of identifying information that can be used in this way will depend upon the third party service used, further definition of which is out of scope for this specification.  For example, a query for a document identified by a DOI, say <code>1234.5678</code>, using the PRISM vocabulary [[PRISM]] recommended by FaBio [[FABIO]], might look like this:</p>
             <pre class="example code">
-  @prefix prov: &lt;<provns/>&gt;
+  @prefix prov: &lt;http://www.w3.org/ns/prov#&gt;
   @prefix prism: &lt;http://prismstandard.org/namespaces/basic/2.0/&gt;
   SELECT ?provenance_uri WHERE
   {
     [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
   }
             </pre>
-          </p>
+          
         </section>
 
         <section>
@@ -631,15 +631,15 @@
             This scenario retrieves provenance information directly given the URI of a resource, and may be useful where the provenance information has not been assigned a specific URI, or when the calling application is interested only in specific elements of provenance information.
           </p>
           <p>
-            If the original resource has a URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this: 
+            If the original resource has a URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this: </p>
             <pre class="example code">
-  @prefix prov: &lt;<provns/>&gt;
+  @prefix prov: &lt;http://www.w3.org/ns/prov#&gt;
   SELECT ?generationStartTime WHERE {
       &lt;http://example.org/resource&gt; prov:wasGeneratedBy ?activity .
       ?activity prov:startedAtTime ?generationStartTime .
   }
             </pre>
-          </p>
+          
           <p>
             This query extracts a "generation start time" for an artifact by following links to the start time of the activity which generated it.
           </p>
@@ -656,14 +656,14 @@
 
         <section>
           <h2>Via Web Retrieval</h2>
-          <p>Publishers are not required to publish all the provenance information associated with a given resource at a particular <a class="internalDFN">provenance-URI</a>. The amount of provenance information exposed is application dependent. However, it is possible to incrementally retrieve (i.e. walk the provenance graph) by progressively looking up provenance information using HTTP. The pattern is as follows:
+          <p>Publishers are not required to publish all the provenance information associated with a given resource at a particular <a class="internalDFN">provenance-URI</a>. The amount of provenance information exposed is application dependent. However, it is possible to incrementally retrieve (i.e. walk the provenance graph) by progressively looking up provenance information using HTTP. The pattern is as follows:</p>
             <ol>
               <li>For a given resource (<code>resource-URI</code>) retrieve it's associated <code>provenance-URI-1</code> and its associated <code>target-URI-1</code> using a returned HTTP <code>Link:</code> header field (<a href="#resource-accessed-by-http" class="sectionRef"></a>)</li>
               <li>Dereference <code>provenance-URI-1</code></li>
               <li>Navigate the provenance information</li>
               <li>When reaching a dead-end during navigation, that is on encountering a reference to a resource (<code>target-URI-2</code>) with no provided provenance information, find its provenance-URI and continue from Step 2.  (Note: an HTTP HEAD request for <code>target-URI-2</code> may be used to obtain the <code>Link:</code> headers without retrieving the resource representation.)</li>
             </ol>
-          </p>
+          
           <p>To reduce the overhead of multiple HTTP requests, a provenance information publishers are encouraged to link entities to their associated provenance information using the <code>prov:hasProvenance</code> predicate. Thus, the same pattern above applies, except instead of having to retrieve a new <code>Link</code> header field, one can immediately access the resource's associated provenance.
           </p>
           <p>The same approach can be adopted when using the <a class="internalDFN">provenance service</a> API (<a href="#provenance-services" class="sectionRef"></a>). However, instead of performing an HTTP HEAD or GET against a resource one queries the provenance service using the given <a class="internalDFN">target-URI</a>.
@@ -691,7 +691,6 @@
       </p>
       <section>
         <h2>Registration template for link relation: "provenance"</h2>
-        <p>
           <dl>
             <dt>Relation Name:</dt>
             <dd>
@@ -714,7 +713,7 @@
               ...
             </dd>
           </dl>
-        </p>
+       
       </section>
       <section>
         <h2>Registration template for link relation: "anchor"</h2>
@@ -745,7 +744,6 @@
       </section>
       <section>
         <h2>Registration template for link relation: "provenance-service"</h2>
-        <p>
           <dl>
             <dt>Relation Name:</dt>
             <dd>
@@ -768,7 +766,7 @@
               ...
             </dd>
           </dl>
-        </p>
+     
       </section>
     </section>
  
@@ -815,7 +813,6 @@
       <p>
         The provenance namespace URI is <provns/>.
       </p>
-      <p>
         <table>
           <tr>
             <th>name</th><th>Description</th><th>Definition ref</th>
@@ -836,7 +833,6 @@
             <td>provenanceUriTemplate</td><td>Relates a provenance service to a URI template string for constructing provenance-URIs</td><td>...</td>
           </tr>
         </table>
-      </p>
     </section>