Remov sha3 reference from the vocabulary table.

Co-authored-by: Manu Sporny <[email protected]>

Author: iherman

index.html

@@ -6978,17 +6978,17 @@ <h3>Vocabularies</h3>
         <p>
 Implementations that depend on RDF vocabulary processing MUST ensure that the
 following vocabulary URLs used in the base context ultimately resolve to the
-following files when loading the JSON-LD serializations, which are normative. Other semantically equivalent
-serializations of the vocabulary files MAY be used by implementations.
-Cryptographic hashes are provided for all the JSON-LD content to ensure that developers can
-verify that the content of each file is correct.
+following files when loading the JSON-LD serializations, which are normative.
+Other semantically equivalent serializations of the vocabulary files MAY be used
+by implementations. A cryptographic hash is provided for each JSON-LD document
+to ensure that developers can verify that the content of each file is correct.
         </p>
 
         <table class="simple">
           <thead>
             <tr>
               <th>URL</th>
-              <th>JSON-LD Content and Hashes</th>
+              <th>JSON-LD Documents and Hashes</th>
             </tr>
           </thead>
           <tbody>
@@ -6999,8 +6999,6 @@ <h3>Vocabularies</h3>
               <td>
 https://www.w3.org/2018/credentials/index.jsonld<br><br>
 sha256: `z52TgKqh2nqTCuACI8lCvhRdjwxQjeVmuOMCDCEijq4=`<br><br>
-sha3-512: <code>m8Ss+jgZiyL2Ws/ICJcWjHFd9PccJWsXPvMatBOhrH<wbr>
-h0qCBrzfgO2zO1OQQbTL7zoPgLseIbcxJJpunD2bkoRA==</code>
               </td>
             </tr>
             <tr>
@@ -7010,18 +7008,16 @@ <h3>Vocabularies</h3>
               <td>
 https://w3c.github.io/vc-data-integrity/vocab/security/vocabulary.jsonld<br><br>
 sha256: `LEaoTyf796eTaSlYWjfPe3Yb+poCW9TjWYTbFDmC0tc=`<br><br>
-sha3-512: <code>f4DhJ3xhT8nT+GZ8UUZi4QC+HT//wXE2fRTgUP4UNw<wbr>
-e4kvel2PFfd6jcofHBm9BjwEiGzVFGv4K+fFTKXRD2NA==</code>
               </td>
             </tr>
           </tbody>
         </table>
 
         <p>
 It is possible to confirm the cryptographic digests listed above by running
-a command like the following (replacing `&lt;DOCUMENT_URL>` and `&lt;DIGEST_ALGORITHM>`
-with appropriate values) through a modern UNIX-like OS command line interface:
-`curl -sL -H "Accept: application/ld+json" &lt;DOCUMENT_URL> | openssl dgst -&lt;DIGEST_ALGORITHM> -binary | openssl base64 -nopad -a`
+a command like the following, replacing `&lt;DOCUMENT_URL>`
+with the appropriate value, through a modern UNIX-like OS command line interface:
+`curl -sL -H "Accept: application/ld+json" &lt;DOCUMENT_URL> | openssl dgst -sha256 -binary | openssl base64 -nopad -a`
         </p>
 
         <p class="note"