fix: typo schema subject (eclipse-dataspace-dcp#204)

* fix: typo in documentation

* fix: VP definition formatting

Author: arnoweiss

specifications/credential.issuance.protocol.md

@@ -76,7 +76,7 @@ the client's [=DID=] to obtain cryptographic material for validation and credent
 
 The ID Token MUST contain a `token` claim that is a bearer token granting write privileges for the
 requested [=Verifiable Credentials=] into the client's `Credential Service` as defined
-by[[[#verifiable-presentation-protocol]]]
+by [[[#verifiable-presentation-protocol]]]
 
 The bearer token MAY also be used by the [=Issuer Service=] to resolve [=Verifiable Presentations=] the client is
 required to hold for issuance of the requested [=Verifiable Credentials=].
@@ -234,7 +234,7 @@ The following is a non-normative example of a credential offer request:
 |              | - `credentialType`: A single string specifying type of credential being offered                                                                                                                                               |
 | **Optional** | - `@context`: Specifies a valid Json-Ld context ([[json-ld11]], sect. 3.1). As the `credentialObject` is usually embedded, its context is provided by the enveloping object.                                                  |
 |              | - `bindingMethods`: An array of strings defining the key material that an issued credential is bound to                                                                                                                       |
-|              | - `credentialSubject`: A URL pointing to the credential schema of the object in a VC's `credentialSubject` property.|
+|              | - `credentialSchema`: A URL pointing to the credential schema of the object in a VC's `credentialSubject` property.                                                                                                           |
 |              | - `profiles`: An array of strings containing the aliases of the [profiles](#profiles-of-the-decentralized-claims-protocol), e.g. `"vc20-bssl/jwt"`                                                                            |
 |              | - `issuancePolicy`: A [presentation definition](https://identity.foundation/presentation-exchange/spec/v2.0.0/#presentation-definition) [[presentation-ex]] signifying the required [=Verifiable Presentation=] for issuance. |
 |              | - `offerReason`: A reason for the offer as a string. Valid values may include `reissue` and `proof-key-revocation`                                                                                                            |

specifications/verifiable.presentation.protocol.md

@@ -192,15 +192,15 @@ when a `presentationDefinition`
 is provided in the [[[#presentation-query-message]]].
 
 ### Presentation Validation
-[=Verifier=] SHOULD validate the [=Verifiable-Presentation=] in the following manner:
-
-1. The [=Verifier=] MUST assert that the [=Verifiable-Presentation=] is created either according to the `scope` or `presentationDefinition`
-2. The [=Verifier=] MUST validate the signature of the [=Verifiable-Presentation=] by using the key obtained from the resolved `VerificationMethod` of the [=Verifiable-Presentation=]. [=DID=] resolution is performed according to the [=DID=] Method specified in the [=DID=] part of the `VerificationMethod` of the [=Verifiable-Presentation=].
-3. The [=Verifier=] MUST validate that the `VerificationMethod` of the [=Verifiable-Presentation=] has the `Authentication` [Verification Relationship](https://www.w3.org/TR/did-1.0/#authentication)
-4. The [=Verifier=] MUST assert that the [=DID=] in the `VerificationMethod` of the [=Verifiable-Credential=] has the same value as the `issuer` of the [=Verifiable-Credential=]. 
-5. The [=Verifier=] MUST validate the signature of the [=Verifiable-Credential=] by using the key obtained from the resolved `VerificationMethod` of the [=Verifiable-Credential=]. [=DID=] resolution is performed according to the [=DID=] Method specified in the [=DID=] part of the `VerificationMethod` of the [=Verifiable-Presentation=].
-6. If the [=Verifiable-Credential=] contains a revocation mechanism, such as `StatusList2021`, the [=Verifier=] MUST validate the status of the [=Verifiable-Credential=] according to the revocation mechanism. 
-7. If the [=Verifiable-Presentation=] contains any claims regarding its `expiryDate` or `validity`, the [=Verifier=] MUST validate those claims.
-8. If any of the steps fail, the [=Verifier=] MUST consider the [=Verifiable-Presentation=] invalid. 
-
-Additionally, if the specific semantics of a data space and credentials require cryptographic holder binding, the [=Verifier=] MUST assert that the `credentialSubject.id` in the [=Verifiable-Credential=] and the [=DID=] part of the `VerificationMethod` of the [=Verifiable-Presentation=] have the same value.
+[=Verifier=] SHOULD validate the [=Verifiable Presentation=] in the following manner:
+
+1. The [=Verifier=] MUST assert that the [=Verifiable Presentation=] is created either according to the `scope` or `presentationDefinition`
+2. The [=Verifier=] MUST validate the signature of the [=Verifiable Presentation=] by using the key obtained from the resolved `VerificationMethod` of the [=Verifiable Presentation=]. [=DID=] resolution is performed according to the [=DID=] Method specified in the [=DID=] part of the `VerificationMethod` of the [=Verifiable Presentation=].
+3. The [=Verifier=] MUST validate that the `VerificationMethod` of the [=Verifiable Presentation=] has the `Authentication` [Verification Relationship](https://www.w3.org/TR/did-1.0/#authentication)
+4. The [=Verifier=] MUST assert that the [=DID=] in the `VerificationMethod` of the [=Verifiable Credential=] has the same value as the `issuer` of the [=Verifiable Credential=]. 
+5. The [=Verifier=] MUST validate the signature of the [=Verifiable Credential=] by using the key obtained from the resolved `VerificationMethod` of the [=Verifiable Credential=]. [=DID=] resolution is performed according to the [=DID=] Method specified in the [=DID=] part of the `VerificationMethod` of the [=Verifiable Presentation=].
+6. If the [=Verifiable Credential=] contains a revocation mechanism, such as `StatusList2021`, the [=Verifier=] MUST validate the status of the [=Verifiable Credential=] according to the revocation mechanism. 
+7. If the [=Verifiable Presentation=] contains any claims regarding its `expiryDate` or `validity`, the [=Verifier=] MUST validate those claims.
+8. If any of the steps fail, the [=Verifier=] MUST consider the [=Verifiable Presentation=] invalid. 
+
+Additionally, if the specific semantics of a data space and credentials require cryptographic holder binding, the [=Verifier=] MUST assert that the `credentialSubject.id` in the [=Verifiable Credential=] and the [=DID=] part of the `VerificationMethod` of the [=Verifiable Presentation=] have the same value.