move section on how to use key attestations in proof types

openid-4-verifiable-credential-issuance-1_0.md

@@ -2294,12 +2294,6 @@ A Wallet MAY provide key attestations to inform the Credential Issuer about the
 
 Key attestations are used by various Credential Issuers with different trust frameworks and requirements, so a common approach is needed for interoperability. Therefore, key attestations SHOULD follow a common format. This helps Credential Issuers create consistent evaluation processes, reducing complexity and errors. Common formats also simplify compliance with regulatory requirements across jurisdictions and support the creation of shared best practices and security standards.
 
-There are two ways to convey key attestations during Credential issuance:
-- The Wallet uses the `jwt` proof type in the Credential Request to create a proof of possession of the key and adds the key attestation in the JOSE header as specified in (#jwt-proof-type).
-- The Wallet uses the `attestation` proof type in the Credential Request with the key attestation without a signature by key(s) themselves as specified in (#attestation-proof-type).
-
-Depending on the Wallet's implementation, the `attestation` may avoid unnecessary End-User interaction during Credential issuance, as the key itself does not necessarily need to perform signature operations.
-
 ## Key Attestation in JWT format {#keyattestation-jwt}
 
 The JWT is signed by the Wallet Provider or the Wallet's key storage component itself and contains the following elements: