Apply editorial suggestions from Joseph's code review

Co-authored-by: Joseph Heenan <joseph@authlete.com>
openid · Nov 28, 2024 · 77aa345 · 77aa345
1 parent 2f4b2ec
commit 77aa345
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-1_0.md b/openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-1_0.md
@@ -96,10 +96,10 @@ defined in [@!ISO.18013-7]. For more details, also see Annex B.3 in [@!OIDF.OID4
 
 ## Standards Requirements
 
-This specification enable interoperable implementation of the following four flows:
+This specification enables interoperable implementation of the following four flows:
 
 * Issuance of IETF SD-JWT VC using OpenID4VCI
-* Presentation of IETF SD-JWT VC using OpenID4VP
+* Presentation of IETF SD-JWT VC using OpenID4VP without using W3C Digital Credentials API
 * Presentation of IETF SD-JWT VC using OpenID4VP over W3C Digital Credentials API
 * Presentation of ISO mdocs using OpenID4VP over W3C Digital Credentials API
 
@@ -206,7 +206,7 @@ This is an example of a Wallet Instance Attestation:
 
 * The Credential Issuer MUST publish a mapping of every Credential Type it supports to a scope value.
 
-# OpenID for Verifiable Presentations without using W3C Digital Credentials API
+# OpenID for Verifiable Presentations profile for SD-JWT VC without using W3C Digital Credentials API
 
    * MUST support protocol extensions for SD-JWT VC credential format profile as defined in this specification (#vc_sd_jwt_profile).
    * As a way to invoke the Wallet, at least a custom URL scheme `haip://` MUST be supported. Implementations MAY support other ways to invoke the wallets as agreed by trust frameworks/ecosystems/jurisdictions, not limited to using other custom URL schemes.