Done with my (final?) review.
--- a/ldpatch.html Fri Nov 21 15:34:11 2014 -0500
+++ b/ldpatch.html Fri Nov 21 15:45:04 2014 -0500
@@ -682,9 +682,9 @@
<li id="cut-nothing">If a <a>Cut</a> operation fails to remove any triple, then a HTTP 422 (Unprocessable Entity) error status code MUST be returned.</li>
<li id="cut-non-bnode">If a <a>Cut</a> operation is called on a variable not bound to a blank node, then a HTTP 422 (Unprocessable Entity) error status code MUST be returned.</li>
<li id="delete-non-existing-triple">If a <a>Delete</a> attempts to remove a non-existing triple, then a HTTP 422 (Unprocessable Entity) error status code MUST be returned.</li>
- <li id="updatelist-non-list-argument">If the <a class="internalDFN" href="#grammar-production-subject">subject</a> and <a class="internalDFN" href="#grammar-production-predicate">predicate</a> provided to an <a>UpdateList</a> do not have a unique object or this object is not a well-formed collection then a HTTP 422 (Unprocessable Entity) error status code MUST be returned.</li>
+ <li id="updatelist-non-list-argument">If the subject and predicate provided to an <a>UpdateList</a> do not have a unique object, or if this object is not a well-formed collection, then a HTTP 422 (Unprocessable Entity) error status code MUST be returned.</li>
<li id="wrong-order-for-indexes">If the indexes in a <a>slice expression</a> are in the wrong order (e.g. <code>2868..42</code>), then the parsing fails and a 400 (Bad Request) error status code MUST be returned.</li>
- <li id="wrong-index">If an index in a <a>slice expression</a> is greated than the length of the <code>rdf:List</code>, then a 422 (Unprocessable Entity) error status code MUST be returned.</li>
+ <li id="wrong-index">If an index in a <a>slice expression</a> is greater than the length of the <code>rdf:List</code>, then a 422 (Unprocessable Entity) error status code MUST be returned.</li>
<li id="unknown-prefix">If a prefix name (<a class="internalDFN" href="#grammar-production-PNAME_NS">PNAME_NS</a>) is used without being previously declared, then the parsing fails and a 400 (Bad Request) error status code MUST be returned.</li>
<li id="unknown-variable">If a <a>var</a>iable is used without being previously bound, then the parsing fails and a 400 (Bad Request) error status code MUST be returned.</li>
@@ -724,7 +724,7 @@
</pre>
<p>
- The blank nodes <code>_:b2</code> and <code>_:b3</code> are unambiguous as they can be reached unambiguoulsy from the literal <code>"W3C/MIT"</code>). The blank node <code>_:b1</code>, on the other hand, is ambigious as all <a>path expression</a>s that can can match it would also match <code>_:b2</code>.
+ The blank nodes <code>_:b2</code> and <code>_:b3</code> are unambiguous as they can be reached unambiguoulsy from the literal <code>"W3C/MIT"</code>. The blank node <code>_:b1</code>, on the other hand, is ambigious as all <a>path expression</a>s that can can match it would also match <code>_:b2</code>.
</p>
<!-- p>
@@ -1223,7 +1223,7 @@
<p>The following people (in alphabetic order) have been instrumental in providing thoughts, feedback, reviews, content, criticism and input in the creation of this specification:</p>
- <p style="margin-left: 3em;">Andy Seaborne, Arnaud Le Hors, Henry Story, John Arwe, Eric Prud'hommeaux, Sandro Hawke, Steve Speicher, Tim Berners-Lee</p>
+ <p style="margin-left: 3em;">Andy Seaborne, Arnaud Le Hors, Ashok Malhotra, Eric Prud'hommeaux, Henry Story, John Arwe, Sandro Hawke, Steve Speicher, Tim Berners-Lee</p>
</section>