Make RFC2119 usages consistent

Author: rubensworks

spec/index.html

@@ -379,8 +379,8 @@ <h2>Introduction</h2>
       of managing a collection of graphs in the REST architectural style.</p>
       <section id="conventions">
         <h3>Document Conventions</h3>
-        <p>When this document uses the words MUST, MUST NOT, SHOULD, SHOULD NOT,
-	        and MAY, and the words appear as emphasized text, they must be
+        <p>When this document uses the words <strong>must</strong>, <strong>must not</strong>, <strong>should</strong>, <strong>should not</strong>,
+	        and <strong>may</strong>, and the words appear as emphasized text, they must be
 	        interpreted as described in [[RFC2119]].
 	      </p>
 
@@ -499,7 +499,7 @@ <h4><code>query</code> via GET</h4>
           all parameters and include them as <a data-cite="rfc3986#section-3.4">query parameter</a> strings [[RFC3986]] with the names given
           above.</p>
           <p>HTTP query string parameters <strong>must</strong> be separated with the ampersand (<code>&amp;</code>) character. Clients may include the query string parameters in any order.</p>
-          <p>The HTTP request <strong>MUST NOT</strong> include a message body.</p>
+          <p>The HTTP request <strong>must not</strong> include a message body.</p>
         </section>
         <section id="query-via-post-urlencoded">
           <h4><code>query</code> via POST with URL-encoded parameters</h4>