Add statement around content intent via cryptographic hashes.

Author: msporny

index.html

@@ -4899,11 +4899,12 @@ <h3>Base Context</h3>
 cryptographically protected by default. It is considered a best practice to
 ensure that the same sorts of protections are provided for any URL that is
 critical to the security of the credential through the use of permanently cached
-files or cryptographic hashes. See the <a
+files and/or cryptographic hashes. See the <a
 data-cite="vc-imp-guide/#content-integrity">Content Integrity</a>
-section of the Verifiable Credential Implementation Guide to verify that content
-that is either fetched remotely or loaded from a local copy is consistent with
-what the <a>issuer</a> or <a>holder</a> intended.
+section of the Verifiable Credential Implementation Guide for further
+information. Ultimately, knowing the cryptographic digest of any externally
+linked content enables a <a>verifier</a> to confirm that the content is the same
+as what the <a>issuer</a> or <a>holder</a> intended.
           </p>
           <p>
 For convenience, the base context for the Verifiable Credential Data Model v2.0