--- a/ldbp.html	Wed Sep 19 15:51:01 2012 -0400
+++ b/ldbp.html	Mon Oct 08 16:50:16 2012 -0400
@@ -290,7 +290,7 @@
 	</div>
 	<div id="bpr-4_1_12" class="rule">4.1.12 BPRs MAY be created, updated and deleted using methods not defined in
 		this document, for example through application-specific means, SPARQL
-		UPDATE, etc. [[!RDF-SPARQL-UPDATE]]
+		UPDATE, etc. [[!SPARQL-UPDATE]]
 	</div>
 	<div id="bpr-4_1_13" class="rule">4.1.13 BPR server responses MUST contain accurate response <code>ETag</code>
 		header values.
@@ -717,7 +717,7 @@
 		a simple case where only a few simple non-member properties are
 		retrieved. In real world situations more complex cases are likely, such as those that add other predicates to
 		containers, for example providing validation information and
-		associating SPARQL endpoints. [[RDF-SPARQL-QUERY]]</p>
+		associating SPARQL endpoints. [[SPARQL-QUERY]]</p>
 	<p>
 		Here is an example requesting the non-member properties of a
 		container identified by the URL <code>http://example.org/container1</code>
@@ -1032,7 +1032,7 @@
 		predicate whose subject is that of the page and object is a list of
 		BPC ordinal predicates.  The default ordering is ascending. The only
 		ordinal predicate literal data types supported are those as defined
-		by SPARQL SELECT’s ORDER BY clause [[!RDF-SPARQL-QUERY]].
+		by SPARQL SELECT’s ORDER BY clause [[!SPARQL-QUERY]].
 	</div>
 	<div id="bpc-5_3_7_1" class="rule">5.3.7.1 The object of <code>bp:containerSortPredicates</code>’,
 		the predicate used to indicate ordering, MUST NOT change between