--- a/model/ProvenanceModel.html	Tue Nov 29 10:23:55 2011 +0000
+++ b/model/ProvenanceModel.html	Tue Nov 29 10:27:38 2011 +0000
@@ -1023,10 +1023,10 @@
 <p>identified by identifier <span class="name">a1</span>, states the existence of an activity with recipe link <span class="name">add-crime-in-london</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span> (declared in some namespace with prefix <span class="name">ex</span>).  The attribute <span class="name">host</span> is application specific, but MUST hold for the duration of activity.  The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for subtyping to be expressed.</p>
 </div>
 
-<p>The mere existence of an activity assertion entails some <a>event</a> ordering in the world, since the <a>activity start event</a> <a>precedes</a> the <a>activity end event</a>.  This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
-
-<div class='interpretation' id='start-precedes-end'> From an activity record, one can infer that the
-<a title="activity start event">start event</a> <a>precedes</a> the <a title="activity end event">end event</a> of the represented activity.</div> 
+<p>The mere existence of an activity assertion entails some <a>event</a> ordering in the world, since an <a>activity start event</a> always <a>precedes</a> the corresponding <a>activity end event</a>.  This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p> 
+
+<div class='interpretation' id='start-precedes-end'> The following temporal constraint holds for any activity record: the
+<a title="activity start event">start event</a> <a>precedes</a> the <a title="activity end event">end event</a>.</div> 
 
 <p>An activity record is not an entity record.
 Indeed, an entity record represents an entity that exists in full at