Fix grammar in changes to address @jyasskin's concerns.

Co-authored-by: Dave Longley <[email protected]>
Co-authored-by: Michael B. Jones <[email protected]>

Author: 3 people

index.html

@@ -794,8 +794,8 @@ <h3>Credentials</h3>
 information, and so on. A
 [=verifiable credential=] is a set of tamper-evident [=claims=] and metadata
 that cryptographically prove who issued it. Examples of [=verifiable
-credentials=] include digital employee identification cards, digital birth
-certificates, and digital educational certificates.
+credentials=] include, but are not limited to, digital employee identification
+cards, digital birth certificates, and digital educational certificates.
         </p>
 
         <figure id="basic-vc">
@@ -886,10 +886,11 @@ <h3>Credentials</h3>
         </figure>
 
         <p class="note">
-[=Credential=] identifiers are often used to identify specific instances
-of a [=credential=]. These identifiers can also be used for correlation. A
-[=holder=] wanting to minimize correlation is advised to use a selective
-disclosure scheme that does not reveal the [=credential=] identifier.
+[=Credential=] identifiers can be used to identify specific instances
+of a [=credential=]. These identifiers could also be used for unwanted
+correlation. A [=holder=] wanting to minimize correlation is advised
+to use a selective disclosure scheme that does not reveal the
+[=credential=] identifier.
         </p>
 
         <p class="note">
@@ -1437,12 +1438,12 @@ <h3>Types</h3>
 [=verifiable credential=] or [=verifiable presentation=] is appropriate
 for the intended use case. This specification defines a `type`
 [=property=] for the expression of object type information. This type
-information can be used during [=validation=] processes as described in Appendix
+information can be used during [=validation=] processes, as described in Appendix
 [[[#validation]]].
         </p>
 
         <p>
-[=Verifiable credentials=] and [=verifiable presentations=] MUST express a
+[=Verifiable credentials=] and [=verifiable presentations=] MUST contain a
 `type` [=property=] with an associated value.
         </p>
 
@@ -1613,7 +1614,7 @@ <h3>Types</h3>
         <p class="note" title="Creating new verifiable credential types">
 Explaining how to create new types of [=verifiable credentials=] is beyond
 the scope of this specification. Readers that are interested in doing so are
-advised to read the Section on
+advised to read the section on
 <a data-cite="?VC-IMP-GUIDE#creating-new-credential-types">
 Creating New Credential Types</a> in the [[[?VC-IMP-GUIDE]]].
         </p>
@@ -3470,7 +3471,7 @@ <h2>Integrity of Related Resources</h2>
 `id` of an object inside a [=conforming document=] need to consider whether
 that resource's content is vital to the validity of that document. If it is, the
 specification MUST produce a validation error unless the resource matches the
-expected media type and cryptographic digest
+expected media type and cryptographic digest.
         </p>
         <p>
 Implementers are urged to consult appropriate sources, such as the
@@ -5368,7 +5369,7 @@ <h3>Identifier-Based Correlation</h3>
         <p>
 [=Securing mechanism=] specification authors are advised to avoid enabling
 identifier-based correlation by designing their technologies, when possible,
-to avoid the use of correlating identifiers.
+to avoid the use of correlating identifiers that cannot be selectively disclosed.
         </p>
 
         <p>