--- a/model/working-copy/towards-wd4.html	Thu Feb 09 23:14:49 2012 +0000
+++ b/model/working-copy/towards-wd4.html	Thu Feb 09 23:16:36 2012 +0000
@@ -1574,7 +1574,7 @@
 </ul>
 
  <div class="anexample">
-<div =class="note"> need an example </div>
+<div class="note"> need an example </div>
 
 </div>
 </section>
@@ -1610,7 +1610,7 @@
 wasInformedBy(s2,s1)
 </pre>
 The last assertions indicates that some entity was generated by  <span class="name">s1</span> and used by  <span class="name">s2</span>.
-</div
+</div>
 
 
 <p>
@@ -1639,7 +1639,7 @@
 activity(a2,t3,t4,[ex:host="server2.example.org",prov:type="subworkflow"])
 wasStartedBy(a2,a1)
 </pre>
-</div
+</div>
 
 </section>
 
@@ -1765,7 +1765,7 @@
 <section id="record-Collection">
 <h3>Collections</h3>
 
-<strong>Collection relations</strong> address the need to describe the evolution of entities that have a collection structure, that is, which may contain other entities. Specifically this section introduces a new built-in type for entities, called <span class="name">collection</span>, and two relations to describe the effect of adding elements to, and removing elements from, a collection entity.
+<p><strong>Collection relations</strong> address the need to describe the evolution of entities that have a collection structure, that is, which may contain other entities. Specifically this section introduces a new built-in type for entities, called <span class="name">collection</span>, and two relations to describe the effect of adding elements to, and removing elements from, a collection entity.
 The intent of these relations and entity types is to capture the <em>history of changes that occurred to a collection</em>. </p>
 
 <p>A collection is an entity that has a logical internal structure consisting of key-value pairs, often referred to as a map.
@@ -1822,13 +1822,13 @@
 <p>Further considerations:</p>
 
 <ul>
-  <li>The <strong>map</strong> collection type provides a generic indexing structure that can be used to model commonly used data structures, including associative lists (also known as "dictionaries" in some programming languages), relational tables, ordered lists, and more (the specification of such specialized structures in terms of key-value pairs is out of the scope of this document).</p>
-
-<li>Keys are literals, and values are entities. This allows expressing nested collections, that is, collections whose values include entities of type collection.</p>
-
-<li>Insertion and removal relations are a particular case of <a href="#Derivation-Relation">derivation</a>.</p>
-
- <li>This representation of a collection's evolution makes no assumption regarding the underlying data structure used to store and manage collections. In particular, no assumptions are needed regarding the mutability of a data structure that is subject to updates.   In fact, the state of a collection (i.e., the set of key-value pairs it contains) at a given point in a sequence of operations is never stated explicitly. Rather, it can be obtained by querying the chain of derivation assertions involving insertions and removals. Entity type <span class="name">emptyCollection</span> can be used in this context as it marks the start of a sequence of collection operations.</p>
+  <li>The <strong>map</strong> collection type provides a generic indexing structure that can be used to model commonly used data structures, including associative lists (also known as "dictionaries" in some programming languages), relational tables, ordered lists, and more (the specification of such specialized structures in terms of key-value pairs is out of the scope of this document).</li>
+
+<li>Keys are literals, and values are entities. This allows expressing nested collections, that is, collections whose values include entities of type collection.</li>
+
+<li>Insertion and removal relations are a particular case of <a href="#Derivation-Relation">derivation</a>.</li>
+
+ <li>This representation of a collection's evolution makes no assumption regarding the underlying data structure used to store and manage collections. In particular, no assumptions are needed regarding the mutability of a data structure that is subject to updates.   In fact, the state of a collection (i.e., the set of key-value pairs it contains) at a given point in a sequence of operations is never stated explicitly. Rather, it can be obtained by querying the chain of derivation assertions involving insertions and removals. Entity type <span class="name">emptyCollection</span> can be used in this context as it marks the start of a sequence of collection operations.</li>
 
 <div class='note'>Delete further items. Some of them are constraints which belong to part 2.</div>