--- a/paq/prov-aq.html	Thu Jan 05 15:23:04 2012 +0000
+++ b/paq/prov-aq.html	Mon Jan 09 10:59:50 2012 +0000
@@ -271,10 +271,10 @@
       <p>
         When <a class="internalDFN">provenance information</a> is a resource that can be accessed using web retrieval, one needs to know a <a class="internalDFN">provenance-URI</a> to dereference.  If this is known in advance, there is nothing more to specify.  If a provenance-URI is not known then a mechanism to discover one must be based on information that is available to the would-be accessor.
       </p>
-      <p>Provenance information may be provided by several parties other than the provider of the original resource, each using different provenance-URIs, and each with different concerns.  (It is possible that these different parties may provide contradictory provenance information.)
+      <p>Provenance information about a resource may be provided by several parties other than the provider of that resource, each using different provenance-URIs, and each with different concerns.  (It is possible that these different parties may provide contradictory provenance information.)
       </p>
       <p>
-      Once provenance information information is retrieved, one also needs to know how to locate the view of that resource within that provenance information. This view is an <a class="internalDFN">entity</a> and is identified by an <a class="internalDFN">entity-URI</a>.
+      Once provenance information about a resource is retrieved, one also needs to know how to locate the view of that resource within that provenance information. This view is an <a class="internalDFN">entity</a> and is identified by an <a class="internalDFN">entity-URI</a>.
       </p>
       <p>
         We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN">provenance-URI</a> along with a <a class="internalDFN">entity-URI</a>.  (Mechanisms that can be independent of the resource provision are discussed in <a href="#provenance-services" class="sectionRef"></a>).  Three mechanisms are described here:
@@ -297,7 +297,7 @@
         <p>
           A <code>provenance</code> link relation type for referencing provenance information is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>, and may be used as shown::
           <pre class="pattern">Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
-          When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
+          When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified within the referenced provenance information as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
         </p>
         <p>
         If no <code>anchor</code> link is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the resource.
@@ -329,7 +329,7 @@
               The <code>provenance-service</code> link identifies the <a class="internalDFN">service-URI</a>.  Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN">provenance-URI</a> or retrieve <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
             </p>
             <p>
-            There may be multiple <code>provenance-service</code> link header fields, and these may appear in the same document as <code>provenance</code> links (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
+            There may be multiple <code>provenance-service</code> link header fields, and these may appear in the same HTTP response as <code>provenance</code> link header fields (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
           </p>
         </section>