Fix grammar in Introduction and Terminology sections.

index.html

@@ -364,7 +364,7 @@ <h3>What is a Verifiable Credential?</h3>
 national agency, or certification body)
           </li>
           <li>
-Information related to the type of [=credential=] this is (for example, a
+Information related to the type of [=credential=] (for example, a
 Dutch passport, an American driving license, or a health insurance card)
           </li>
           <li>
@@ -373,7 +373,9 @@ <h3>What is a Verifiable Credential?</h3>
 the classes of vehicle entitled to drive, or date of birth)
           </li>
           <li>
-Evidence related to how the [=credential=] was derived
+Evidence related to how the qualifications required for the [=credential=]
+to be issued were met by the [=subject=] (for example, a measurement,
+proof of citizenship, or test result)
           </li>
           <li>
 Information related to constraints on the credential (for example,
@@ -707,21 +709,20 @@ <h2>Terminology</h2>
         </dd>
         <dt><dfn class="export" data-lt="claim validation|validate">validation</dfn></dt>
         <dd>
-The assurance that a [=claim=] from a specific [=issuer=] satisfies the
-business requirements of a [=verifier=] for a particular use. This
-specification defines how verifiers verify [=verifiable credentials=] and
-[=verifiable presentations=].<br/>
-It also specifies that [=verifiers=] validate claims in [=verifiable
-credentials=] before relying on them. However, the means for such validation
-vary widely and are outside the scope of this specification. [=Verifiers=]
-trust certain [=issuers=] for certain claims and apply their own rules to
-determine which claims in which [=credentials=] are suitable for use by their
-systems.
+The assurance that a [=claim=] from a specific [=issuer=] satisfies the business
+requirements of a [=verifier=] for a particular use. This specification defines
+how verifiers verify [=verifiable credentials=] and [=verifiable
+presentations=]. It also specifies that [=verifiers=] validate claims in
+[=verifiable credentials=] before relying on them. However, the means for such
+validation vary widely and are outside the scope of this specification.
+[=Verifiers=] trust certain [=issuers=] for certain claims and apply their own
+rules to determine which claims in which [=credentials=] are suitable for use by
+their systems.
         </dd>
         <dt><dfn class="export">verifiable credential</dfn></dt>
         <dd>
-A verifiable credential is a tamper-evident credential that has authorship that
-can be cryptographically verified. Verifiable credentials can be used to build
+A tamper-evident [=credential=] that has authorship that can be
+cryptographically verified. Verifiable credentials can be used to build
 [=verifiable presentations=], which can also be cryptographically verified.
         </dd>
         <dt><dfn class="export" data-lt="verifiable data registries">verifiable data registry</dfn></dt>
@@ -736,20 +737,20 @@ <h2>Terminology</h2>
         </dd>
         <dt><dfn class="export">verifiable presentation</dfn></dt>
         <dd>
-A verifiable presentation is a tamper-evident presentation encoded in such a way
-that authorship of the data can be trusted after a process of cryptographic
+A tamper-evident presentation of information encoded in such a way that
+authorship of the data can be trusted after a process of cryptographic
 verification. Certain types of verifiable presentations might contain data that
-is synthesized from, but do not contain, the original [=verifiable
-credentials=] (for example, zero-knowledge proofs).
+is synthesized from, but do not contain, the original [=verifiable credentials=]
+(for example, zero-knowledge proofs).
         </dd>
         <dt><dfn class="export" data-lt="verify|verified|verifying|verifiable|verifiability">verification</dfn></dt>
         <dd>
 The evaluation of whether a [=verifiable credential=] or [=verifiable
-presentation=] is an authentic and current statement of the issuer or
-presenter, respectively. This includes checking that: the credential (or
-presentation) conforms to the specification; the proof method is satisfied; and,
-if present, the status check succeeds. Verification of a credential does not
-imply evaluation of the truth of [=claims=] encoded in the credential.
+presentation=] is an authentic and current statement of the issuer or presenter,
+respectively. This includes checking that: the credential or presentation
+conforms to the specification; the securing mechanism is satisfied; and, if
+present, the status check succeeds. Verification of a credential does not imply
+evaluation of the truth of [=claims=] encoded in the credential.
         </dd>
         <dt><dfn class="export" data-lt="verifier|verifiers|verifier's|credential verifiers|credential verifier's">verifier</dfn></dt>
         <dd>
@@ -766,11 +767,11 @@ <h2>Terminology</h2>
         </dd>
         <dt><dfn data-lt="URL|URLs">URL</dfn></dt>
         <dd>
-A Uniform Resource Locator, as defined by [[URL]]. URLs can be dereferenced such
-that they result in a resource, such as a document. The rules for dereferencing,
-or fetching, a URL are defined by the URL [=url/scheme=]. This specification
-does not use the term URI or IRI because those terms have been deemed to be
-confusing to Web developers.
+A Uniform Resource Locator, as defined by the [[[URL]]]. URLs can be
+dereferenced such that they result in a resource, such as a document. The rules
+for dereferencing, or fetching, a URL are defined by the URL [=url/scheme=].
+This specification does not use the term URI or IRI because those terms have
+been deemed to be confusing to Web developers.
         </dd>
       </dl>
     </section>