Fix "field"->"property" since we use the latter in this spec.

index.html

@@ -581,7 +581,7 @@ <h3>Ecosystem Overview</h3>
         </p>
 
         <p class="note" title="Human-readable texts in English are illustrative">
-Examples provided throughout this document include descriptive fields, such as
+Examples provided throughout this document include descriptive properties, such as
 `name` and `description`, with values in English to simplify the concepts in each
 example of the specification. These examples do not necessarily reflect the data
 structures needed for international use, described in more detail in
@@ -4473,19 +4473,19 @@ <h3>Media Type Precision</h3>
 Parse the payload as a JSON document.
             </li>
             <li>
-Ensure that the first element of the `@context` field matches
+Ensure that the first element of the `@context` property matches
 `https://www.w3.org/2018/credentials/v2`.
             </li>
             <li>
 Assume an `application/vp` media type if the JSON document contains a
-top-level `type` field containing a `VerifiablePresentation` element. Additional
+top-level `type` property containing a `VerifiablePresentation` element. Additional
 subsequent checks are still expected to be performed (according to this
 specification) to ensure the payload expresses a conformant Verifiable
 Presentation.
             </li>
             <li>
 Assume an `application/vc` media type if the JSON document contains a
-top-level `type` field containing a `VerifiableCredential` element. Additional
+top-level `type` property containing a `VerifiableCredential` element. Additional
 subsequent checks are still expected to be performed (according to this
 specification) to ensure the payload expresses a conformant Verifiable
 Credential.
@@ -4965,7 +4965,7 @@ <h3>Personally Identifiable Information</h3>
 
         <p>
 Data associated with [=verifiable credentials=] stored in the
-`credential.credentialSubject` field is susceptible to privacy violations when
+`credential.credentialSubject` property is susceptible to privacy violations when
 shared with [=verifiers=]. Personally identifying data, such as a
 government-issued identifier, shipping address, and full name, can be easily
 used to determine, track, and correlate an [=entity=]. Even information that
@@ -6450,7 +6450,7 @@ <h2>Validation</h2>
 information in this data model is expected to be utilized by [=verifiers=]
 during the process of [=validation=]. This section captures a selection of
 conversations held by the Working Group related to the expected usage of the
-data fields in this specification by [=verifiers=].
+properties in this specification by [=verifiers=].
       </p>
 
       <section class="informative">
@@ -7438,7 +7438,7 @@ <h2>Revision History</h2>
 Provide more explicit guidance around sets and arrays.
         </li>
         <li>
-Add support for `name` and `description` fields for issuers and credentials.
+Add support for `name` and `description` properties for issuers and credentials.
         </li>
         <li>
 Add security considerations around interception, replay, and spoofing attacks.