--- a/model/glossary.html	Mon Apr 02 09:09:31 2012 +0100
+++ b/model/glossary.html	Mon Apr 02 09:20:14 2012 +0100
@@ -43,7 +43,7 @@
 </span>
 
 <span class="glossary" id="glossary-account">  
-An <dfn id="concept-account">account</dfn> is an entity that contains a bundle of provenance assertions. 
+An <dfn id="concept-account">account</dfn> is an entity that contains a bundle of provenance descriptions. 
 </span>
 
 <span class="glossary" id="glossary-provenance">  

--- a/model/prov-dm-constraints.html	Mon Apr 02 09:09:31 2012 +0100
+++ b/model/prov-dm-constraints.html	Mon Apr 02 09:20:14 2012 +0100
@@ -492,8 +492,8 @@
 
 
 
-    <section  id="account-and-accountEntity">
-      <h3>Account and AccountEntity</h3>
+    <section  id="account-section">
+      <h3>Account</h3>
 
 
 <p>It is common for multiple provenance records to co-exist. For
@@ -513,28 +513,24 @@
 
 <p>
   <span  class="glossary" id="glossary-account">
-An <dfn>account</dfn> is a named bundle of provenance descriptions.
+An <dfn>account</dfn> is a entity that contains a bundle of provenance descriptions.
 </span>  PROV-DM does not provide an actual mechanism for creating accounts, i.e. for bundling up provenance descriptions and naming them.  Accounts MUST satisfy some properties:
 <ul>
-<li>An account can be seen as a container of provenance descriptions, hence its content MAY change over time.</li>
+<li>An account is as a container of provenance descriptions, hence its content MAY change over time.</li>
 <li>If an account's  set of descriptions changes over time, it increases monotonically with time. </li>
 <li>A given description of e.g. an entity in a given account, in terms of its identifier and attribute-value pairs, does not change over time. </li>
 </ul>
 
 <div class='note'>
-The last point is important and needs to be discussed by the Working Group.
-It indicates that within an account:
+The last point is important. It indicates that within an account:
 <ul>
-<li>It is always possible to add new provenance descriptions, e.g. stating that a given entity was used by an activity.  This is very much an open world assumption.
+<li>It is always possible to add new provenance descriptions, e.g. stating that a given entity was used by an activity, or derived from another.  This is very much an open world assumption.
 <li>It is not permitted to add new attributes to a given entity (a form of closed world assumption from the attributes point of view), though it is always permitted to create a new description for an entity, which is a "copy" of the original description extended with novel attributes  (cf Example <a href="#merge-with-rename">merge-with-rename</a>).
 </ul>
 </div>
 
 <p>
-There is no construct in PROV-DM to create such named bundles. Instead, it is assumed that some mechanism, outside PROV-DM can create them.  However, from a provenance viewpoint, such accounts are things we may want to describe the provenance of. In order to be able to do so, we need to see accounts as entities, whose origin can be described using PROV-DM vocabulary. Thus, PROV-DM introduces the reserved type AccountEntity, defined as follows:
-<span  class="glossary" id="glossary-entity">
- <dfn id="concept-accountEntity">AccountEntity</dfn> is the category of entities that are accounts, i.e. named bundles of provenance descriptions.
-</span>
+There is no construct in PROV-DM to create such bundles of descriptions. Instead, it is assumed that some mechanism, outside PROV-DM can create them.  However, from a provenance viewpoint, such accounts are things we may want to describe the provenance of. In order to be able to do so, we need to see accounts as entities, whose origin can be described using PROV-DM vocabulary. Thus, PROV-DM introduces the reserved type <span class="name">Account</span>.
 </p>
 
     </section>