CSP 1.1: Denormify the hash mismatch warning.

We don't really want to have normative requirements for things like
console messages. Changing the SHOULD to a non-normative note.

Author: mikewest

csp-specification.dev.html

@@ -702,18 +702,19 @@ <h5>Valid Hashes</h5>
                     <a href="http://csrc.nist.gov/groups/STM/cavp/documents/shs/sha256-384-512.pdf">defined by the NIST</a>)
                   </li>
                   <li>Let <var>expected</var> be the <code>hash-value</code> component of <var>hash</var>.</li>
-                  <li>Let <var>actual</var> be the <a href="http://tools.ietf.org/html/rfc4648#section-4">base64 encoding</a> of
-                      the binary <a href="#dfn-digest-of-an-elements-contents"><var>algorithm</var> digest of <var>element</var>'s
-                      contents</a>.</li>
+                  <li>Let <var>actual</var> be the <a href="http://tools.ietf.org/html/rfc4648#section-4">base64 encoding</a>
+                  of the binary <a href="#dfn-digest-of-an-elements-contents"><var>algorithm</var> digest of <var>element</var>'s
+                  contents</a>.</li>
                   <li>If <var>actual</var> is a case-sensitive match for
                   <var>expected</var>, return true and abort these steps.</li>
                 </ol>
               </li>
               <li>Return false.</li>
             </ol>
 
-            <p>If the user agent fails to match <code>hash-value</code>, the user agent SHOULD report a warning message in the developer console
-               containing the <var>actual</var> hash value.</p>
+            <p>Note that if an element has an invalid hash, it would be helpful
+            if the user agent reported the failure to the author by adding
+            a warning message containing the <var>actual</var> hash value.</p>
         </section>
 
         <section>