Update all text to specify the SHA-256 hash function rather than SHAK…

…E-256.

index.html

@@ -464,7 +464,7 @@ <h2>Algorithms</h2>
       <p>
 The following algorithms describe how to use verifiable credentials with
 the BBS Signature Scheme [[CFRG-BBS-SIGNATURE]]. When using the BBS signature
-scheme the SHAKE-256 variant SHOULD be used.
+scheme the SHA-256 variant SHOULD be used.
       </p>
 
       <p>
@@ -647,7 +647,7 @@ <h4>createDisclosureData</h4>
             </li>
             <li>
 Initialize `hmac` to an HMAC API using `hmacKey`. The HMAC uses the same hash
-algorithm used in the signature algorithm, i.e., SHAKE-256.
+algorithm used in the signature algorithm, i.e., SHA-256.
             </li>
             <li>
 Initialize `labelMapFactoryFunction` to the result of calling the
@@ -725,7 +725,7 @@ <h4>createDisclosureData</h4>
 algorithm [[RDF-CANON]] on `proof` with the `proofValue` removed and then
 cryptographically
 hashing the result using the same hash that is used by the signature algorithm,
-i.e., SHAKE-256. Note: This step can be performed in parallel;
+i.e., SHA-256. Note: This step can be performed in parallel;
 it only needs to be completed before this algorithm terminates, as the result is
 part of the return value.
                 </li>
@@ -734,7 +734,7 @@ <h4>createDisclosureData</h4>
 <a href="https://www.w3.org/TR/vc-di-ecdsa/#hashmandatorynquads">Section 3.3.17
 hashMandatoryNQuads</a> of the [[DI-ECDSA]] specification, passing the values
 from the map
-<var>groups.mandatory.matching</var> and utilizing the SHAKE-256 algorithm.
+<var>groups.mandatory.matching</var> and utilizing the SHA-256 algorithm.
                 </li>
                 <li>
 Set  `bbsHeader` to the concatenation of `proofHash` and `mandatoryHash` in that
@@ -944,7 +944,7 @@ <h4>createVerifyData</h4>
 Initialize `proofHash` to the result of performing RDF Dataset Canonicalization
 [[RDF-CANON]] on the proof options, i.e., the proof  portion of the document
 with the `proofValue` removed. The hash used is the same as that used in
-the signature algorithm, i.e., SHA-256 for a P-256 curve. Note: This step can be
+the signature algorithm, i.e., SHA-256. Note: This step can be
 performed in parallel; it only needs to be completed before this algorithm needs
 to use the `proofHash` value.
             </li>
@@ -1055,7 +1055,7 @@ <h4>Base Proof Transformation (bbs-2023)</h4>
             <li>
 Initialize `hmac` to an HMAC API using a locally generated and exportable HMAC
 key. The HMAC uses the same hash algorithm used in the signature algorithm,
-i.e., SHAKE-256.
+i.e., SHA-256.
             </li>
             <li>
 Initialize `labelMapFactoryFunction` to the result of calling the
@@ -1116,15 +1116,15 @@ <h4>Base Proof Hashing (bbs-2023)</h4>
 Initialize `proofHash` to the result of calling the RDF Dataset Canonicalization
 algorithm [[RDF-CANON]] on `canonicalProofConfig` and then cryptographically
 hashing the result using the same hash that is used by the signature algorithm,
-i.e., SHAKE-256. Note: This step can be performed in parallel;
+i.e., SHA-256. Note: This step can be performed in parallel;
 it only needs to be completed before this algorithm terminates, as the result is
 part of the return value.
             </li>
             <li>
 Initialize `mandatoryHash` to the result of calling the the algorithm in
 <a href="https://www.w3.org/TR/vc-di-ecdsa/#hashmandatorynquads">Section 3.3.17
 hashMandatoryNQuads</a> of the [[DI-ECDSA]] specification, passing
-<var>transformedDocument</var>.`mandatory` and utilizing the SHAKE-256
+<var>transformedDocument</var>.`mandatory` and utilizing the SHA-256
 algorithm.
             </li>
             <li>
@@ -2186,8 +2186,8 @@ <h4>Base Proof</h4>
           <pre class="example nohighlight" title="Canonical Base Proof Configuration" data-include="TestVectors/addProofConfigCanon.txt"
           data-include-format="text"></pre>
           <p>
-In the hashing step, we compute the SHAKE-256 hash of the canonicalized proof
-options to produce the `proofHash`, and we compute the SHAKE-256 hash of the
+In the hashing step, we compute the SHA-256 hash of the canonicalized proof
+options to produce the `proofHash`, and we compute the SHA-256 hash of the
 join of all the mandatory N-Quads to produce the `mandatoryHash`. These are
 shown below in hexadecimal format.
           </p>