Apply suggestions from WG discussion

Co-authored-by: Joseph Heenan <joseph@authlete.com>

Author: Sakurann

openid4vc-high-assurance-interoperability-profile-1_0.md

@@ -326,13 +326,15 @@ Wallet implementations using the key attestation format specified in Annex D of
 
 This document intentionally leaves certain extensions for ecosystems to define, in order to enable broad compatibility across differing or even conflicting requirements. These include:
 
-- Which Credential format to support across issuance and presentation.
-- Whether to use Signed Issuer Metadata or not.
-- How to send Credential Offer.
-- Key attestation formats.
-- X509 certificate profiles.
-- Whether to use DC API, Redirects with custom URL schemes  and/or Redirects with claimed "https" scheme URIs for presentation. 
-- Support or restriction of additional cryptographic suites and hash algorithms.
+- Whether to adopt the Presentation profile, Issuance profile, or both
+- Which Credential format to support across issuance and presentation
+- Whether to use Signed Issuer Metadata or not
+- How to send Credential Offer
+- Which Key attestation format to use
+- Which Wallet attestation format to use
+- X509 certificate profiles
+- Whether to use DC API, Redirects with custom URL schemes  and/or Redirects with claimed `https` scheme URIs for presentation
+- Support or restriction of additional cryptographic suites and hash algorithms
 
 Below are two non-normative examples illustrating how an ecosystem may define the above elements to achieve its specific goals and preferences.
 
@@ -349,7 +351,7 @@ Making these choices maximizes interoperability between the parties in the ecosy
 
 ### Existing Curve Requirements
 
-This ecosystem places importance on maintaining backward compatibility with already issued cryptographic curves. To achieve this, the ecosystem could define the following:
+This ecosystem places importance on maintaining compatibility with already issued cryptographic curves. To achieve this, the ecosystem could define the following:
 
 - Verifiers MUST support all curves from Cipher Suite 1 as listed in table 22 of (@!ISO.18013-5).
 - Verifiers MUST support all hash algorithms in table 21 of (@!ISO.18013-5).