rationalize credential repositories/credential repository/repositories/repository

partial handling of #1475

Author: TallTed

index.html

@@ -522,15 +522,15 @@ <h2>Terminology</h2>
 associated with an [=entity=]. These identifiers are most often used in a
 [=verifiable credential=] and are associated with [=subjects=] such that a
 [=verifiable credential=] itself can be easily ported from one
-[=repository=] to another without the need to reissue the [=credential=].
+[=credential repository=] to another without the need to reissue the [=credential=].
 An example of a DID is `did:example:123456abcdef`.
         </dd>
         <dt><dfn class="lint-ignore" data-lt="decentralized identifier documents|DID document|DID documents">decentralized identifier document</dfn></dt>
         <dd>
 Also referred to as a <strong><em>DID document</em></strong>, this is a document
 that is accessible using a [=verifiable data registry=] and contains
 information related to a specific [=decentralized identifier=], such as the
-associated [=repository=] and [=verification material=].
+associated [=credential repository=] and [=verification material=].
         </dd>
         <dt><dfn data-lt="default graph">default graph</dfn></dt>
         <dd>
@@ -608,7 +608,7 @@ <h2>Terminology</h2>
 Data derived from one or more [=verifiable credentials=], issued by one or
 more [=issuers=], that is shared with a specific [=verifier=].
         </dd>
-        <dt><dfn class="export" data-lt="credential repository|credential repositories|repositories">repository</dfn></dt>
+        <dt><dfn class="export" data-lt="credential repositories">credential repository</dfn></dt>
         <dd>
 A program, such as a storage vault or personal [=verifiable credential=]
 wallet, that stores and protects access to [=holders'=]
@@ -2807,7 +2807,7 @@ <h3>Trust Model</h3>
 quickly if and when they no longer stand by those [=claims=].
           </li>
           <li>
-The [=holder=] expects the [=repository=] to store [=credentials=] securely,
+The [=holder=] expects the [=credential repository=] to store [=credentials=] securely,
 to not release [=credentials=] to anyone other than the [=holder=] (which may
 subsequently present them to a [=verifier=]), and to not corrupt nor lose
 [=credentials=] while they are in its care.
@@ -2822,7 +2822,7 @@ <h3>Trust Model</h3>
         <ul>
           <li>
 The [=issuer=] and [=verifier=] do not need to know anything about the
-[=repository=].
+[=credential repository=].
           </li>
           <li>
 The [=issuer=] does not need to know anything about the [=verifier=].
@@ -5456,7 +5456,7 @@ <h3>Storage Providers and Data Mining</h3>
         <p>
 When a [=holder=] receives a [=verifiable credential=] from an
 [=issuer=], the [=verifiable credential=] needs to be stored somewhere
-(for example, in a [=credential=] repository). [=Holders=] are warned that
+(for example, in a [=credential repository=]). [=Holders=] are warned that
 the information in a [=verifiable credential=] is sensitive in nature and
 highly individualized, making it a high value target for data mining. Services
 that advertise free storage of [=verifiable credentials=] might in fact be
@@ -5465,7 +5465,7 @@ <h3>Storage Providers and Data Mining</h3>
         </p>
         <p>
 [=Holders=] need to be aware of the terms of service for their
-[=credential=] repository, specifically the correlation and data mining
+[=credential repository=], specifically the correlation and data mining
 protections in place for those who store their [=verifiable credentials=]
 with the service provider.
         </p>
@@ -6083,7 +6083,7 @@ <h3>Device Theft and Impersonation</h3>
           </li>
           <li>
 Enabling password, biometric, or multi-factor authentication for the
-[=credential=] [=repository=].
+[=credential repository=].
           </li>
           <li>
 Enabling password, biometric, or multi-factor authentication when accessing