--- a/ldp-bp/ldp-bp.html	Sat Jul 06 16:37:19 2013 -0500
+++ b/ldp-bp/ldp-bp.html	Sat Jul 06 19:46:39 2013 -0500
@@ -134,7 +134,7 @@
 				<dt>best practice</dt>
 				<dd>
 					A good implementation practice (method or technique) that has consistently shown results superior to those achieved with other means and that is used as a benchmark. Best practices within this document apply specifically to the ways that one should implement technology (i.e. LDP servers, clients, and related systems). In this document, the best practices might be used as a kind of check-list against which one can directly evaluate a system's design and code. Lack 
-					of adherance to any given best practice, however, does not necessarily imply a lack of quality; they are recommendations that are said to be 'best' in most 
+					of adherence to any given best practice, however, does not necessarily imply a lack of quality; they are recommendations that are said to be 'best' in most 
 					cases and in most contexts, but not all. A best practice is always subject to improvement as we learn and evolve the Web together.
 				</dd>
 				<dt>guideline</dt>
@@ -182,7 +182,7 @@
 			<p>This provides a way for clients to easily determine the type of a resource without having to perform additional 
 				processing or make additional HTTP requests. For example, clients that cannot infer the type because they do not support inferencing can benefit from this explicit declaration.</p>
 
-			<pre title="Turtle With Explicit Declaration of rdf:type" class='example' data-include='include-rdf-type.ttl' data-oninclude='fixCode'></pre>
+			<pre title="Turtle with explicit declaration of rdf:type" class='example' data-include='include-rdf-type.ttl' data-oninclude='fixCode'></pre>
 		
 		</section>
 
@@ -518,15 +518,27 @@
 	</section>
 
 	<section>
+
 		<h2>Guidelines</h2>
+		
 		<section>
-			<h3>Guideline 1</h3>
-			<p>Eplurbis unum...</p>
+			
+			<h3>Containers are not limited to same-subject, same-predicate triples</h3>
+			
+			<p>
+			The LDP specification defines a Container as &quot;a Linked Data Platform Resource (LDPR) representing a collection of same-subject, same-predicate triples.&quot; This can easily be misconstrued to mean that a Container should <em>only</em> contain same-subject, same-predicate triples. While Containers <em>may</em> contain only same-subject, same-predicate triples (i.e. the membership subjects and membership predicates of its membership triples), it is free to contain others. The definition is meant to clarify only those attributes that are directly relavant to the interaction model of a Container, but not to limit them to those attributes alone. 
+			</p>
+
+			<p>It is important to remember that a Linked Data Platform Container (LDPC) is also a Linked Data Platform Resource (LDPR) and though it might exist as a membership controller, it may also represent additional data that is valuable to the agents that access it.</p>
+
 		</section>
+
+		<!--
 		<section>
 			<h3>Guideline 2</h3>
 			<p>Eplurbis unum...</p>
 		</section>
+		-->
 	</section>
 
 	<section>