--- a/model/working-copy/towards-wd4.html	Thu Feb 09 23:16:36 2012 +0000
+++ b/model/working-copy/towards-wd4.html	Thu Feb 09 23:17:43 2012 +0000
@@ -1830,7 +1830,6 @@
 
  <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>
 
 <!-- 
   <li> One can have multiple assertions regarding the state of a collection following a <em>set</em> of insertions, for example:<br/>
@@ -1905,6 +1904,7 @@
 Here  <span class="name">c3</span> includes <span class="name">{ (k2 v2) }</span> but the earlier "gap" leaves uncertainty regarding  <span class="name">(k1,v1)</span>  (it may have been removed) or any other pair that may have been added as part of the derivation activities.</li></p>
 -->
 </ul>
+<div class='note'>Deleted further items. Some of them are constraints which belong to part 2.</div>
 
 
 </section>   <!-- end collections-->