Fix "public key" and "verification material" usage.

Author: msporny

index.html

@@ -397,8 +397,8 @@ <h3>Ecosystem Overview</h3>
           <dt>[=verifiable data registry=]</dt>
           <dd>
 A role a system might perform by mediating the creation and [=verification=]
-of identifiers, keys, and other relevant data, such as
-[=verifiable credential=] schemas, revocation registries, issuer public keys,
+of identifiers, [=verification material=], and other relevant data, such as
+[=verifiable credential=] schemas, revocation registries,
 and so on, which might be required to use [=verifiable credentials=]. Some
 configurations might require correlatable identifiers for [=subjects=].
 Example verifiable data registries include trusted databases, decentralized
@@ -526,7 +526,7 @@ <h2>Terminology</h2>
 Also referred to as a <strong><em>DID document</em></strong>, this is a document
 that is accessible using a [=verifiable data registry=] and contains
 information related to a specific [=decentralized identifier=], such as the
-associated [=repository=] and public key information.
+associated [=repository=] and [=verification material=].
         </dd>
         <dt><dfn data-lt="default graph">default graph</dfn></dt>
         <dd>
@@ -646,12 +646,12 @@ <h2>Terminology</h2>
         <dt><dfn class="export" data-lt="verifiable data registries">verifiable data registry</dfn></dt>
         <dd>
 A role a system might perform by mediating the creation and [=verification=]
-of identifiers, keys, and other relevant data, such as
-[=verifiable credential=] schemas, revocation registries, issuer public keys,
+of identifiers, [=verification material=], and other relevant data, such as
+[=verifiable credential=] schemas, revocation registries,
 and so on, which might be required to use [=verifiable credentials=]. Some
 configurations might require correlatable identifiers for [=subjects=]. Some
-registries, such as ones for UUIDs and public keys, might just act as namespaces
-for identifiers.
+registries, such as ones for UUIDs and [=verification material=], might just act
+as namespaces for identifiers.
         </dd>
         <dt><dfn class="export">verifiable presentation</dfn></dt>
         <dd>
@@ -679,8 +679,9 @@ <h2>Terminology</h2>
         </dd>
         <dt><dfn data-lt="verification material">verification material</dfn></dt>
         <dd>
-Information that could be a cryptographic public key or any other data used to
-verify a proof.
+Information that is used to verify the security of cryptographically
+protected information. For example, a cryptographic public key used to verify
+a digital signature associated with a [=verifiable credential=].
         </dd>
         <dt><dfn data-lt="URL|URLs">URL</dfn></dt>
         <dd>
@@ -6785,9 +6786,9 @@ <h3>Proofs (Signatures)</h3>
           <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
-authentication or encryption, of the public key.
+is a cryptographic 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 cryptographic public key.
           </li>
           <li>
 The public key is not suspended, revoked, or expired.
@@ -7017,7 +7018,7 @@ <h3>Vocabularies</h3>
         </table>
 
         <p>
-It is possible to confirm the cryptographic digests listed above by running 
+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`