Skip to content

Commit 21a0755

Browse files
mspornyTallTeddlongley
committed
Fix grammar in verification material language.
Co-authored-by: Ted Thibodeau Jr <[email protected]> Co-authored-by: Dave Longley <[email protected]>
1 parent a41d544 commit 21a0755

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

index.html

+5-5
Original file line numberDiff line numberDiff line change
@@ -735,7 +735,7 @@ <h3>Credentials</h3>
735735
[=entity=]. [=Credentials=] might also include an identifier and metadata
736736
to describe properties of the [=credential=], such as the
737737
[=issuer=], the validity date and time period, a representative image,
738-
verification material to use for [=verification=] purposes, the revocation
738+
[=verification material=], the revocation
739739
mechanism, and so on. The metadata might be signed by the [=issuer=]. A
740740
[=verifiable credential=] is a set of tamper-evident [=claims=] and
741741
metadata that cryptographically prove who issued it.
@@ -5787,7 +5787,7 @@ <h3>Key Management</h3>
57875787
provides recommendations for protective measures, harm reduction, and
57885788
revocation. Although this section focuses primarily on the security of the
57895789
private signing key, [[NIST-SP-800-57-Part-1]] also highly recommends
5790-
confirmation of the validity of all verification material before using it.
5790+
confirmation of the validity of all [=verification material=] before using it.
57915791
</p>
57925792
</section>
57935793

@@ -6339,7 +6339,7 @@ <h3>Credential Subject</h3>
63396339
`credentialSubject` is expected to identify a [=subject=] to the
63406340
[=verifier=]. If the [=holder=] is also the [=subject=], then
63416341
the [=verifier=] could authenticate the [=holder=] if they have
6342-
verification material metadata related to the [=holder=]. The [=verifier=]
6342+
[=verification=] metadata related to the [=holder=]. The [=verifier=]
63436343
could then authenticate the [=holder=] using a signature generated by the [=holder=]
63446344
contained in the [=verifiable presentation=]. The `id`
63456345
[=property=] is optional. [=Verifiers=] could use other [=properties=]
@@ -6390,7 +6390,7 @@ <h4>Holder</h4>
63906390
Often relevant metadata about the [=holder=], as identified by the value of
63916391
the `holder` [=property=], is available to, or retrievable by, the
63926392
[=verifier=]. For example, a [=holder=] can publish information containing
6393-
the verification material used to secure [=verifiable presentations=]. This
6393+
the [=verification material=] used to secure [=verifiable presentations=]. This
63946394
metadata is expected to be used when checking proofs on [=verifiable presentations=].
63956395
Some cryptographic identifiers contain all necessary metadata in the identifier itself.
63966396
In those cases, no additional metadata is required. Other identifiers use verifiable data
@@ -6483,7 +6483,7 @@ <h3>Proofs (Signatures)</h3>
64836483

64846484
<ul>
64856485
<li>
6486-
Acceptably recent metadata regarding the verification material associated
6486+
Acceptably recent metadata regarding the [=verification material=] associated
64876487
with the signature is available. For example, the metadata might include
64886488
[=properties=] related to validity periods, key owner, or key purpose.
64896489
</li>

terms.html

+1-1
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@
200200
</dd>
201201
<dt><dfn data-lt="verification material">verification material</dfn></dt>
202202
<dd>
203-
Cryptographic information could be a public key or any other cryptographic data
203+
Information that could be a cryptographic public key or any other data
204204
used to verify a proof.
205205
</dd>
206206
<dt><dfn data-lt="URL|URLs">URL</dfn></dt>

0 commit comments

Comments
 (0)