--- a/ldp.html	Tue Jul 23 16:17:25 2013 -0400
+++ b/ldp.html	Wed Jul 24 07:16:13 2013 -0400
@@ -1426,7 +1426,7 @@
 	</div>
 	
 	<div id="ldpc-5_4_3" class="rule">5.4.3 LDPC servers MAY accept an HTTP <code>POST</code> of non-RDF representations for
-		creation of any kind of resource, for example binary resources.  See <a href="#ldpr-5_4_13">5.4.13</a> for introspection
+		creation of any kind of resource, for example binary resources.  See <a href="#ldpc-5_4_13">5.4.13</a> for introspection
 		details.
 	</div>
 	<div id="ldpc-5_4_4" class="rule">5.4.4 For servers that support create, LDPC servers MUST create an LDPR from a
@@ -1477,7 +1477,7 @@
 	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>	
-	<div id="ldpr-5_4_13" class="rule">5.4.13 LDPR servers that support <code>POST</code> MUST
+	<div id="ldpc-5_4_13" class="rule">5.4.13 LDPR servers that support <code>POST</code> MUST
 		include an <a href="#header-accept-post"><code>Accept-Post</code> response header</a> on HTTP <code>OPTIONS</code>
 		responses, listing post document media type(s) supported by the server.
 		LDP only specifies the use of <code>POST</code> for the purpose of creating new resources, but a server
@@ -1493,7 +1493,7 @@
 		specifications such as LDP.
 	</div>
 		
-	<div id="ldpr-5_4_14" class="rule">5.4.14 LDPCs that create new member resources MAY add triples to the container 
+	<div id="ldpc-5_4_14" class="rule">5.4.14 LDPCs that create new member resources MAY add triples to the container 
 		as part of member creation to reflect its factory role.  
 		LDP defines the <code>ldp:created</code> predicate for this purpose.  
 		An LDPC that tracks members created through the LDPC MUST add a triple