--- a/paq/working/prov-aq.html	Thu Apr 26 06:56:00 2012 -0400
+++ b/paq/working/prov-aq.html	Thu Apr 26 12:24:42 2012 +0100
@@ -172,8 +172,8 @@
 
     <section id='abstract'>
 This document specifies how to use standard Web protocols,
-including HTTP, to obtain information about the provenance of Web
-resources. We describe both simple access mechanisms for
+including HTTP, to obtain information about the provenance of
+resources on the Web. We describe both simple access mechanisms for
 locating provenance information associated with web pages or resources, and
 provenance query services for more complex deployments. This is
 part of the larger W3C Prov provenance framework.
@@ -249,7 +249,7 @@
             <dt><dfn>Service-URI</dfn></dt>
             <dd>the URI of a <a class="internalDFN">provenance service</a>.</dd>
             <dt><dfn>Resource</dfn></dt>
-            <dd>also referred to as <dfn>web resource</dfn>: a resource as described by the Architecture of the World Wide Web [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
+            <dd>also referred to as <dfn>resource on the Web</dfn>: a resource as described by the Architecture of the World Wide Web [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
           </dl>
         </p>
 
@@ -258,7 +258,7 @@
       <section>
         <h2 id="provenance-entities-resources">Provenance and resources</h2>
         <p>
-          Fundamentally, <a class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resource</a>s.  In general, resources may vary over time and context.  E.g., a resource describing the weather in London changes from day-to-day, or one listing restaurants near you will vary depending on your location.  Provenance information, to be useful, must be persistent and not itself dependent on context.  Yet we may still want to make provenance assertions about dynamic or context-dependent web resources (e.g. the weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
+          Fundamentally, <a class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resource</a>s.  In general, resources may vary over time and context.  E.g., a resource describing the weather in London changes from day-to-day, or one listing restaurants near you will vary depending on your location.  Provenance information, to be useful, must be persistent and not itself dependent on context.  Yet we may still want to make provenance assertions about dynamic or context-dependent resources (e.g. the weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
         </p>
         <p>
           Provenance descriptions of dynamic and context-dependent resources are possible through a notion of constrained resources.  A <a class="internalDFN">constrained resource</a> is simply a resource (in the sense defined by [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>) that is a contextualized view or instance of some other resource.  For example, a W3C specification typically undergoes several public revisions before it is finalized.  A URI that refers to the "current" revision might be thought of as denoting the specification through its lifetime.  Separate URIs for each individual revision would also have <a class="internalDFN">target-uri</a>s, each denoting the specification at a particular stage in its development.  Using these, we can make provenance assertions that a particular revision was published on a particular date, and was last modified by a particular editor.  Target-URIs may use any URI scheme, and are not required to be dereferencable.
@@ -288,7 +288,7 @@
     <section>
       <h2>Accessing provenance information</h2>
       <p>
-        Web applications may access <a class="internalDFN">provenance information</a> in the same way as any web resource, by dereferencing its URI. Thus, any provenance information may be associated with a <a class="internalDFN">provenance-URI</a>, and may be accessed by dereferencing that URI using web mechanisms.
+        Web applications may access <a class="internalDFN">provenance information</a> in the same way as any resource on the Web, by dereferencing its URI. Thus, any provenance information may be associated with a <a class="internalDFN">provenance-URI</a>, and may be accessed by dereferencing that URI using web mechanisms.
       </p>
       <p>
         How much or how little provenance information is returned in response to a retrieval request is a matter for the provenance provider application.  
@@ -560,7 +560,7 @@
       <section id="querying-provenance-information">
         <h2>Using SPARQL for provenance queries</h2>
         <p>
-          Simply identifying and retrieving provenance information as a web resource 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.:
           <ul>
             <li>the resource for which provenance information is required is not identified by a known URI</li>
             <li>the provenance information for an resource is not directly identified by a known URI</li>