--- a/ontology/prov-o-html-sections/description-expanded-terms.inc.html	Tue Jul 03 14:01:03 2012 -0400
+++ b/ontology/prov-o-html-sections/description-expanded-terms.inc.html	Tue Jul 03 14:10:35 2012 -0400
@@ -31,7 +31,7 @@
       <p>
       A <span class="repeated">prov:Bundle</span> is a named set of provenance descriptions that enables the expression of provenance of provenance.
       It is important to note that the set of provenance descriptions can assume forms beyond PROV-O triples, such as videotaped testimony or scribbles on a drink napkin. 
-      The extension of Bundle that contains only PROV-O assertions is not named by PROV or PROV-O, since it is more appropriate to do so using other recommendations, 
+      The subclass of Bundle that contains PROV-O assertions is not provided by PROV-O, since it is more appropriate to do so using other recommendations, 
       standards, or technologies. In any case, a Bundle of PROV-O assertions is an abstract set of RDF triples, and adding or removing a triple creates a distinct 
       Bundle of PROV-O assertions.
 		</p>

--- a/ontology/prov-o-html-sections/description-starting-points.inc.html	Tue Jul 03 14:01:03 2012 -0400
+++ b/ontology/prov-o-html-sections/description-starting-points.inc.html	Tue Jul 03 14:10:35 2012 -0400
@@ -19,8 +19,6 @@
       <a href='#used' class="qname">prov:used</a> and <a href='#wasGeneratedBy' class="qname">prov:wasGeneratedBy</a>, respectively). 
       For example, a blog writing activity may use a particular dataset and generate a bar chart. 
       Provenance chains of alternating Activities and Entities can be created by applying usage and generation.
-      Arbitrary RDF properties can be used to describe the fixed aspects of an Entity that are interesting to a particular application (for example, 
-      the file size and format of the dataset, or the aspect ratio of the bar chart).
       </p>
 
       <p>In addiition, we can say that an Activity <a href='#wasInformedBy' class="qname">prov:wasInformedBy</a>
@@ -29,9 +27,11 @@
       Activity, but the Entity itself is not interesting. So, the <span class="repeated">prov:wasInformedBy</span> property allows the assertion of provenance chains comprising only Activities.
       </p>
 
-      <p>The <a href='#wasDerivedFrom' class="qname">prov:wasDerivedFrom</a> property can be used to form provenance chains of only Entities.
+      <p>Property chains of Entities can be formed using the <a href='#wasDerivedFrom' class="qname">prov:wasDerivedFrom</a> property.
          A derivation is a transformation of one entity into another. For example, if the Activity that created the bar chart is not interesting,
-          the we can say that the bar chart <span class="repeated">prov:wasDerivedFrom</span> the dataset.
+          then we can say that the bar chart <span class="repeated">prov:wasDerivedFrom</span> the dataset.
+         Arbitrary RDF properties can be used to describe the fixed aspects of an Entity that are interesting to a particular application (for example, 
+         the file size and format of the dataset, or the aspect ratio of the bar chart).
       </p>
 
       <p>An Agent can be responsible for an Activity or an Entity, which is described using the properties <a href='#wasAssociatedWith' class="qname">prov:wasAssociatedWith</a> and <a href='#wasAttributedTo' class="qname">prov:wasAttributedTo</a>, respectively. Agents can also be responsible for other Agents' actions. In this case, the Agent that influenced an Activity or Entity <a href='#actedOnBehalfOf' class="qname">prov:actedOnBehalfOf</a> another Agent that may have had less influence, but still bears some responnsibility for the resulting Activity or Entity.