--- a/ldp-bp/ldp-bp.html	Thu Jun 05 11:50:28 2014 -0400
+++ b/ldp-bp/ldp-bp.html	Mon Jun 09 07:35:26 2014 -0500
@@ -705,6 +705,10 @@
 						<td>Floating-point number type as specified by XSD Float</td>
 					</tr>
 					<tr>
+						<td><a href="http://www.w3.org/2001/XMLSchema#hexBinary">http://www.w3.org/2001/XMLSchema#hexBinary</a></td>
+						<td>Arbitrary hex-encoded binary data as specified by XSD hexBinary</td>
+					</tr>
+					<tr>
 						<td><a href="http://www.w3.org/2001/XMLSchema#integer">http://www.w3.org/2001/XMLSchema#integer</a></td>
 						<td>Integer number type as specified by XSD Integer</td>
 					</tr>
@@ -908,8 +912,7 @@
 		</section>
 
 		<section>
-			<h3>Respond with canonical URLs and use them for identity
-				comparison</h3>
+			<h3>Respond with canonical URLs and use them for identity comparison</h3>
 
 			<p>Clients can access an LDPR using multiple URLs. An LDPR server
 				should respond to each of those requests using a single consistent
@@ -918,7 +921,7 @@
 				potentially also in the representation of the LDPR. A common case is
 				URLs that vary by protocol, one HTTP and one HTTPS, but are
 				otherwise identical. In most cases those two URLs refer to the same
-				resource, and the server should respond to requests to either URL
+				resource, and the server should respond to requests on either URL
 				with a single (canonical) URL.</p>
 
 			<p>Clients should use the canonical URL as an LDPR's identity;