--- a/ldp.html	Sat Mar 02 16:51:18 2013 -0500
+++ b/ldp.html	Mon Mar 04 08:21:11 2013 -0500
@@ -577,13 +577,13 @@
 		members of a container. This document also explains how to include
 		information about each member in the container’s own representation
 		and how to paginate the container representation if it gets too big.</p>
-	<p>The model for containers follow that of strong composition.  Due to composition
+	<p>The model for containers follow that of two distinct types: composition and aggregation.  Due to composition
 	   constraints, the lifespan of the member resource must match that of its container and it a member resource 
-	   can not be a member of more than one container. Members are 
+	   can not be a member of more than one container. For both types of containers, members are 
 	   only added by using POST, which both creates the resource and inserts a membership triple.
-	   A request to delete a container that has members, will result in all 
+	   A request to delete a composite container that has members, will result in all 
 	   the members and the container itself will be deleted. A member resource is removed
-	   from a container by deleting the resource directly, which removes the
+	   from a composite container by deleting the resource directly, which removes the
 	   membership triple from the container.</p>
 	<p>The following illustrates a very simple
 		container with only three members and some information about the
@@ -1163,13 +1163,11 @@
 		(for example, the member is managed by the same server), the LDPC server MUST also remove it from
 		the LDPC by removing the corresponding membership triple.
 	</div>	
-	<div id="ldpc-5_6_2" class="rule">5.6.2 If a LDPC server supports deletion of the LDPC, 
-		and the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:AggregateContainer</code>,
+	<div id="ldpc-5_6_2" class="rule">5.6.2 When the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:AggregateContainer</code>,
 		the server MAY also delete the resources that are referenced as its contents.  
 		The LDPC membership triple MUST also be updated as defined by <a href="#ldpc-5_6_1">5.6.1</a> above.
 	</div>
-	<div id="ldpc-5_6_3" class="rule">5.6.3 If a LDPC server supports deletion of the LDPC, 
-		and the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:CompositeContainer</code>,
+	<div id="ldpc-5_6_3" class="rule">5.6.3 When the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:CompositeContainer</code>,
 		the server MUST also delete the resources that are referenced as its contents.  
 		The LDPC membership triple MUST also be updated as defined by <a href="#ldpc-5_6_1">5.6.1</a> above.
 	</div>
@@ -1229,6 +1227,7 @@
 <h1>Change History</h1>
 <blockquote><em>First Public Working Draft</em></blockquote>
 <ul>
+	<li>2013-03-03 - Adjustments to language about different container behavior (SS)</li>
 	<li>2013-03-02 - Adding trailing '/' on Container URLs to help with readability based on WG suggestion (SS)</li>
 	<li>2013-02-26 - Updated Acknowledgements section (SS)</li>
 	<li>2013-02-25 - ISSUE-29 - Use relative URIs in examples (SS)</li>