Change "cryptographic signature" to "digital signature".

index.html

@@ -6705,24 +6705,25 @@ <h3>Issuance Date</h3>
         <h3>Proofs (Signatures)</h3>
 
         <p>
-The securing mechanism used to prove that the information in a
-[=verifiable credential=] or [=verifiable presentation=] was not tampered
-with is called a <em>cryptographic proof</em>. There are many types of cryptographic proofs
+The securing mechanism used to prove that the information in a [=verifiable
+credential=] or [=verifiable presentation=] was not tampered with is called a
+<em>cryptographic proof</em>. There are many types of cryptographic proofs
 including, but not limited to, digital signatures and zero-knowledge proofs. In
 general, when verifying cryptographic proofs, implementations are expected to
 ensure:
         </p>
 
         <ul>
           <li>
-The cryptographic proof is available in a form defined by a known cryptographic suite.
+The cryptographic proof is available in a form defined by a known cryptographic
+suite.
           </li>
           <li>
 All required cryptographic proof [=properties=] are present.
           </li>
           <li>
-The cryptographic proof [=verification=] algorithm, when applied to the data, results in an
-accepted cryptographic proof.
+The cryptographic proof [=verification=] algorithm, when applied to the data,
+results in an accepted cryptographic proof.
           </li>
         </ul>
 
@@ -6733,18 +6734,17 @@ <h3>Proofs (Signatures)</h3>
 
         <ul>
           <li>
-Acceptably recent metadata regarding the [=verification material=]
-associated with the signature is available. For example, if the
-[=verification material=] is a public key, the
-metadata might include [=properties=] related to the validity period,
-the controller, or the authorized purpose, such as
+Acceptably recent metadata regarding the [=verification material=] associated
+with the signature is available. For example, if the [=verification material=]
+is a public key, the metadata might include [=properties=] related to the
+validity period, the controller, or the authorized purpose, such as
 authentication or encryption, of the public key.
           </li>
           <li>
 The public key is not suspended, revoked, or expired.
           </li>
           <li>
-The cryptographic signature is expected to verify.
+The digital signature is expected to verify.
           </li>
           <li>
 Any additional requirements defined by the securing mechanism are satisfied.