Note that a VerifiableCredentialGraph contains a single VC.

index.html

@@ -2248,21 +2248,22 @@ <h4>Verifiable Credential Graphs</h4>
           </p>
 
           <p>
-To ensure that data from different <a>verifiable credentials</a> are
-not accidentally co-mingled, the concept of a
+To ensure that data from different <a>verifiable credentials</a> are not
+accidentally co-mingled, the concept of a
 <dfn class="lint-ignore">verifiable credential graph</dfn> is used to
 encapsulate each <a>verifiable credential</a>. Each value associated with the
 `verifiableCredential` property of a <a>presentation</a> is of type
-<dfn class="lint-ignore">VerifiableCredentialGraph</dfn>. Using this type has a
-concrete effect on full JSON-LD processing, which properly separates graph
-node identifiers in one graph from those in another graph. Implementers that do not
-fully process JSON-LD will need to keep this in mind if they merge data
-from one <a>verifiable credential</a> with data from another, such as when the
-`credentialSubject.id` is the same in both <a>verifiable credentials</a>, but
-the object might contain objects of the "Jane Doe" form described in the
-previous paragraph. It is important to not merge objects that use
-document-relative identifiers, such as blank node identifiers, and to only
-perform merges when global identifiers, such as URLs, are used.
+<dfn class="lint-ignore">VerifiableCredentialGraph</dfn> and contains a single
+<a>verifiable credential</a>. Using this type has a concrete effect on full
+JSON-LD processing, which properly separates graph node identifiers in one graph
+from those in another graph. Implementers that do not fully process JSON-LD will
+need to keep this in mind if they merge data from one <a>verifiable
+credential</a> with data from another, such as when the `credentialSubject.id`
+is the same in both <a>verifiable credentials</a>, but the object might contain
+objects of the "Jane Doe" form described in the previous paragraph. It is
+important to not merge objects that use document-relative identifiers, such as
+blank node identifiers, and to only perform merges when global identifiers, such
+as URLs, are used.
           </p>
         </section>
 
@@ -5681,7 +5682,7 @@ <h4>Holder</h4>
 publish information containing the verification material used to secure
 <a>verifiable presentations</a>. This metadata is expected to be used when
 checking proofs on <a>verifiable presentations</a>. Some cryptographic
-identifiers contain all necessary metadata in the identifier itself. In those 
+identifiers contain all necessary metadata in the identifier itself. In those
 cases, no additional metadata is required. Other identifiers use verifiable
 data registries where such metadata is automatically published for use
 by <a>verifiers</a>, without any additional action by the <a>holder</a>.
@@ -5692,7 +5693,7 @@ <h4>Holder</h4>
         </p>
 
         <p class="note">
-Validation is the process by which verifiers apply business rules to 
+Validation is the process by which verifiers apply business rules to
 evaluate the propriety of a particular use of a <a>verifiable credential</a>.
         </p>
         <ul>
@@ -5710,11 +5711,11 @@ <h4>Holder</h4>
         </p>
         <ul>
           <li>
-The <a>verifiable presentation</a> is secured, 
+The <a>verifiable presentation</a> is secured,
 using a mechanism the <a>verifier</a> trusts to protect the integrity of the content.
           </li>
           <li>
-The <a>verifiable presentation</a> includes one or more <a>verifiable credentials</a> that are secured, 
+The <a>verifiable presentation</a> includes one or more <a>verifiable credentials</a> that are secured,
 using a mechanism the <a>verifier</a> trusts to protect the integrity of the content.
           </li>
           <li>