--- a/model/prov-dm.html	Tue Apr 17 02:07:56 2012 +0200
+++ b/model/prov-dm.html	Tue Apr 17 09:30:13 2012 +0100
@@ -1623,22 +1623,22 @@
 
 
 <div class="anexample">
-<p>The following descriptions state the existence of derivations.</p>
+<p>The following descriptions are about derivations between  <span class="name">e2</span> and  <span class="name">e1</span>, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</p>
 <pre class="codeexample">
 wasDerivedFrom(e2, e1)
 wasDerivedFrom(e2, e1, [prov:type="physical transform"])
+</pre>
+<p>The following description expresses that activity  <span class="name">a</span>, 
+using the entity <span class="name">e1</span> according to usage <span class="name">u1</span>,
+ derived the
+entity <span class="name">e2</span> and generated it according to generation
+ <span class="name">g2</span>. It is followed by descriptions for generation <span class="name">g2</span> and usage <span class="name">u1</span>.</p>
+<pre class="codeexample">
 wasDerivedFrom(e2, e1, a, g2, u1)
 wasGeneratedBy(g2, e2, a, -)
 used(u1, a, e1, -)
 </pre>
-<p>
-The first and second lines are about derivations between  <span class="name">e2</span> and  <span class="name">e1</span>, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</p>
-<p>
-The third description expresses that activity  <span class="name">a</span>, 
-using the entity <span class="name">e1</span> according to usage <span class="name">u1</span>,
- derived the
-entity <span class="name">e2</span> and generated it according to generation
- <span class="name">g2</span>. It is followed by descriptions for generation <span class="name">g2</span> and usage <span class="name">u1</span>. With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the original entity <span class="name">e1</span> was used by  the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity <span class="name">e2</span> was obtained from (say, for a function returning multiple results).</p>
+<p>With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the original entity <span class="name">e1</span> was used by  the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity <span class="name">e2</span> was obtained from (say, for a function returning multiple results).</p>
 </div>