--- a/ldp.html	Tue Jul 09 07:29:43 2013 -0400
+++ b/ldp.html	Tue Jul 09 08:05:53 2013 -0400
@@ -1422,10 +1422,10 @@
 	</div>
 	
 	<div id="ldpc-5_4_12" class="rule">5.4.12 Upon successful creation of a non-RDF and therefore non-LDPR member (HTTP status code of 
-	201-Created and URI indicated by <code>Location</code>) response header, LDPC servers MAY create an associated LDPR
+	201-Created and URI indicated by <code>Location</code> response header), LDPC servers MAY create an associated LDPR
 	to contain data about the created resource.  If an LDPC Server creates this associated LDPR it MUST indicate
 	its location on the HTTP response using the HTTP response header <code>Link</code> and relationship type <code>meta</code>
-	and <code>href</code> to be the URI of the meta-resource. [[!RFC5988]]</div>	
+	and <code>href</code> to be the URI of the meta-resource [[!RFC5988]].</div>	
 	
 	<div class="ldp-issue-pending">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/80">ISSUE-80</a></div>
@@ -1591,11 +1591,11 @@
 		would be <code>Link: &lt;?nonMemberProperties&gt;;rel="http://www.w3.org/ns/ldp#non-member-resource"</code>
 	</div>
 	
-	<div id="ldpc-5_9_2" class="rule">5.9.2 When a LDPC member non-LDPR (e.g. binary) originally created by the LDPC (for example, one whose 
-	representation was HTTP POST'd to the LDPC and then referenced by a membership triple) it might have created an associated LDPR to contain data about the 
-	non-LDPR (see <a href="#ldpc-5_4_12">5.4.12</a>).  For non-LDPRs that have this associated LDPR, an LDPC server provide an HTTP <code>Link</code>
-	header whose target URI is the <a>associated LDPR</a>, and whose link relation type is 
-	<code>meta</code> [[!RFC5988]]</div>
+	<div id="ldpc-5_9_2" class="rule">5.9.2 When a LDPC creates a non-LDPR (e.g. binary) member (for example, one whose 
+	representation was HTTP POST'd to the LDPC and then referenced by a membership triple) it might create an associated LDPR to contain data about the 
+	non-LDPR (see <a href="#ldpc-5_4_12">5.4.12</a>).  For non-LDPRs that have this associated LDPR, an LDPC server MUST provide an HTTP <code>Link</code>
+	header whose target URI is the associated LDPR, and whose link relation type is 
+	<code>meta</code> [[!RFC5988]].</div>
 </section>
 </section>