--- a/paq/provenance-access.html	Thu Nov 17 17:52:42 2011 +0000
+++ b/paq/provenance-access.html	Thu Nov 17 18:10:00 2011 +0000
@@ -169,7 +169,7 @@
           Provenance descriptions of dynamic and context-dependent resources are possible through the notion of entities.  An <a class="internalDFN">entity</a> is simply a web resource that is a contextualized view or instance of an original web 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 then be <a class="internalDFN">entity-URIs</a>, 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.  Entity-URIs may use any URI scheme, and are not required to be dereferencable.
         </p>
         <p>
-           Requests for provenance about a resource may return provenance information that uses one or more entity-URIs to refer to it.  Some given provenance information may use multiple entity-URIs if there are assertions referring to the same underlying resource in different contexts.  For example, provenance information describing a W3C document might include information about all revisions of the document using statements that use the different entity-URIs of the various revisions.
+           Requests for provenance about a resource may return provenance information that uses one or more entity-URIs to refer to versions of that resource.  Some given provenance information may use multiple entity-URIs if there are assertions referring to the same underlying resource in different contexts.  For example, provenance information describing a W3C document might include information about all revisions of the document using statements that use the different entity-URIs of the various revisions.
         </p>
         <p>
           In summary, a key notion within the concepts outlined above is that <a class="internalDFN">provenance information</a> may be not universally applicable to a <a class="internalDFN">resource</a>, but may be expressed with respect to that resource in a restricted context (e.g. at a particular time). This restricted view is called an <a class="internalDFN">entity</a>, and an <a class="internalDFN">entity-URI</a> is used to refer to it within provenance information.