--- a/model/working-copy/towards-wd4.html	Wed Feb 15 21:33:28 2012 +0000
+++ b/model/working-copy/towards-wd4.html	Wed Feb 15 21:43:24 2012 +0000
@@ -226,7 +226,7 @@
 provenance <em>interchange</em> model across such systems.</p>
 
 <p>A set of specifications, referred to as the PROV family of specifications, define the various aspects
-that are necessary to achieve this vision in an inter-operable
+that are necessary to achieve this vision in an interoperable
 way:</p>
 <ul>
 <li>A data model for provenance, which is presented in three documents:
@@ -338,9 +338,9 @@
 
 <p>
 <div class="glossary" id="glossary-activity">
-An <dfn id="concept-activity">activity</dfn> is anything that involves
-entities; this involvement can take multiple forms:  consuming them,  processing them, 
-transforming them,  modifying them,  changing them,  relocating
+An <dfn id="concept-activity">activity</dfn> is anything that acts upon or with
+entities; this action can take multiple forms:  consuming them,  processing them, 
+transforming them,  modifying them,  relocating
 them,  using them,  generating them, being associated with them,
 etc. Activities that operate on digital entities may for example move, copy, or duplicate them.
 </div>
@@ -875,7 +875,7 @@
 
 
 <p>
-From an inter-operability perspective, it is useful to define some basic categories of agents since
+From an interoperability perspective, it is useful to define some basic categories of agents since
 it will improve the use of provenance by applications.  
 There should be very few of these basic categories to keep the model simple and accessible. 
 There are three types of agents in the model since they are common across most anticipated domains of use:
@@ -908,7 +908,7 @@
 
 <p>As provenance descriptions are exchanged between systems, it may be useful to add extra-information to what they are describing. For instance, a "trust service" may add value-judgements about the
 trustworthiness of some of the entities or agents involved. Likewise, an interactive visualization component may want to enrich a set of provenance descriptions with information helping reproduce their
-visual representation. To help with inter-operability, PROV-DM introduces a simple annotation mechanism allowing anything that is identifiable to be associated with notes.</p>
+visual representation. To help with interoperability, PROV-DM introduces a simple annotation mechanism allowing anything that is identifiable to be associated with notes.</p>
 
 <p>A <dfn title="dfn-note">note</dfn><span class="withAsn">, noted <span class="name">note(id, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
 <ul>
@@ -2117,7 +2117,7 @@
 <li>Domain specific values can be expressed by means of typed literals. </li>
 </ul>
 
-<p>The PROV data model is designed to be application and technology independent, but specializations of PROV-DM are welcome and encouraged.  To ensure inter-operability, specializations of
+<p>The PROV data model is designed to be application and technology independent, but specializations of PROV-DM are welcome and encouraged.  To ensure interoperability, specializations of
 the PROV data model that exploit the extensibility points summarized in this section MUST preserve the semantics specified in the PROV-DM documents (part 1 to 3). </p>