--- a/model/ProvenanceModel.html	Sun Jan 22 14:34:26 2012 -0500
+++ b/model/ProvenanceModel.html	Mon Jan 23 15:03:06 2012 +0000
@@ -3496,7 +3496,7 @@
 
 We adopt a very generic form of collection for the purpose, namely an abstract data types consisting of <strong>set of key-value pairs</strong>, often referred to as a <strong>map</strong>. This provides a generic indexing structure that can be used to model commonly used data structures, including associative lists (also known as "dictionaries" or maps 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/>
 
-Keys and values used in collections are either literals, or entities themselves. This allows expressing nested collections, that is, collections whose values include entities of type collection.<p/>
+Keys and values used in collections are literals. This allows expressing nested collections, that is, collections whose values include entities of type collection.<p/>
 
 <p>The following relations and corresponding record types are introduced to model (a) insertion of a new key-value pair into a collection and (b) removal of a key-value pair from a collection.
 
@@ -3522,7 +3522,7 @@
 </ul>
 
 <div class="note">Given the specific nature of the derivation, the intervening activity that accounts for imprecise-1 derivation should have an equally specific type, such as"
-collection-insertion" and "collection-removal". This is left for a future version.</div>
+collection-insertion" and "collection-rmoval". This is left for a future version.</div>
 
 The intent of these relations and entity types is to capture the <em>history of changes that occurred to a collection</em>. <p/>