minor changes in Issuer capitalization

Author: samuelmr

index.html

@@ -362,7 +362,7 @@ <h4 id="issuer-metadata-publication"><a class="toc-anchor" href="#issuer-metadat
 <p><strong>Requirement: The Credential Issuer MUST place the public key material of the keys it uses to sign Digital Credentials in the <code>jwt_vc_issuer</code> property. The <code>jwt_vc_issuer</code> property MUST include the <code>jwks</code> property that contains the Issuer’s JSON Web Key Set as defined in RFC7517.</strong> (The <code>jwt_vc_issuer</code> property MUST NOT include the <code>jwks_uri</code> property.)</p>
 <p><strong>Requirement: If the <code>openid_credential_issuer</code> property is found in the Entity Configuration, the Wallet MUST use only it and ignore the issuer metadata published in the well-known location defined in OID4VCI.</strong></p>
 <p>The Credential Issuer MAY place additional metadata into the <code>federation_entity</code> Entity Type Identifier.</p>
-<p><strong>Requirement: The metadata in the <code>openid_credential_issuer</code> property MUST override the metadata in the <code>federation_entity</code> property.</strong> For example, if both <code>openid_credential_issuer.display.name</code> and <code>federation_entity.organization_name</code> exist, the Wallet MUST show the value of <code>openid_credential_issuer.display.name</code> as the name of the issuer.</p>
+<p><strong>Requirement: The metadata in the <code>openid_credential_issuer</code> property MUST override the metadata in the <code>federation_entity</code> property.</strong> For example, if both <code>openid_credential_issuer.display.name</code> and <code>federation_entity.organization_name</code> exist, the Wallet MUST show the value of <code>openid_credential_issuer.display.name</code> as the name of the Issuer.</p>
 <h4 id="example-credential-issuer-entity-configuration"><a class="toc-anchor" href="#example-credential-issuer-entity-configuration" >§</a> Example: Credential Issuer Entity Configuration</h4>
 <p>The following JSON document is a non-normative example of the decoded payload of a Credential Issuer’s Entity Configuration.</p>
 <pre class="language-json"><code class="language-json"><span class="token punctuation">{</span>
@@ -479,7 +479,7 @@ <h4 id="client-identifier-scheme"><a class="toc-anchor" href="#client-identifier
 <h4 id="verifier-metadata-publication"><a class="toc-anchor" href="#verifier-metadata-publication" >§</a> Verifier Metadata Publication</h4>
 <p><strong>Requirement: The Verifier MUST place verifier metadata into the Entity Configuration, in the <code>openid_credential_verifier</code> property.</strong></p>
 <h3 id="trust-establishment-3"><a class="toc-anchor" href="#trust-establishment-3" >§</a> Trust Establishment</h3>
-<p><strong>Requirement: To establish trust with the issuer (ensure that the issuer can be trusted), the Verifier MUST resolve the Trust Chain from the issuer’s Entity Configuration until it finds a Federation Entity it trusts.</strong>
+<p><strong>Requirement: To establish trust with the Issuer (ensure that the Issuer can be trusted), the Verifier MUST resolve the Trust Chain from the Issuer’s Entity Configuration until it finds a Federation Entity it trusts.</strong>
 <strong>Requirement: The Verifier MUST verify that the credential is signed with a key included in the <code>jwt_vc_issuer</code> metadata in the Entity Configuration of the Issuer. The <code>jwks</code> property in the <code>jwt_vc_issuer</code> must contain a key with the <code>kid</code> value equal to the <code>kid</code> header in the <a class="term-reference" href="#term:sd-jwt-vc">SD-JWT VC</a> credential.</strong></p>
 <h4 id="example-verifier-entity-configuration"><a class="toc-anchor" href="#example-verifier-entity-configuration" >§</a> Example: Verifier Entity Configuration</h4>
 <p>The following JSON document is a non-normative example of the decoded payload of a Verifier’s Entity Configuration.</p>

spec/federation-profile.md

@@ -54,7 +54,7 @@ The Credential Issuer's Entity Configuration can be found by appending the strin
 
 The Credential Issuer MAY place additional metadata into the `federation_entity` Entity Type Identifier.
 
-**Requirement: The metadata in the `openid_credential_issuer` property MUST override the metadata in the `federation_entity` property.** For example, if both `openid_credential_issuer.display.name` and `federation_entity.organization_name` exist, the Wallet MUST show the value of `openid_credential_issuer.display.name` as the name of the issuer.
+**Requirement: The metadata in the `openid_credential_issuer` property MUST override the metadata in the `federation_entity` property.** For example, if both `openid_credential_issuer.display.name` and `federation_entity.organization_name` exist, the Wallet MUST show the value of `openid_credential_issuer.display.name` as the name of the Issuer.
 
 #### Example: Credential Issuer Entity Configuration
 
@@ -199,7 +199,7 @@ If the Issuer chooses to make this kind of distinction between the entity issuin
 
 ### Trust Establishment
 
-**Requirement: To establish trust with the issuer (ensure that the issuer can be trusted), the Verifier MUST resolve the Trust Chain from the issuer's Entity Configuration until it finds a Federation Entity it trusts.**
+**Requirement: To establish trust with the Issuer (ensure that the Issuer can be trusted), the Verifier MUST resolve the Trust Chain from the Issuer's Entity Configuration until it finds a Federation Entity it trusts.**
 **Requirement: The Verifier MUST verify that the credential is signed with a key included in the `jwt_vc_issuer` metadata in the Entity Configuration of the Issuer. The `jwks` property in the `jwt_vc_issuer` must contain a key with the `kid` value equal to the `kid` header in the [[ref: SD-JWT VC]] credential.**
 
 #### Example: Verifier Entity Configuration