eu-digital-identity-wallet · skounis · Sep 11, 2024 · Sep 5, 2024 · Sep 6, 2024 · Sep 11, 2024
diff --git a/docs/annexes/annex-1/annex-1-definitions.md b/docs/annexes/annex-1/annex-1-definitions.md
@@ -70,7 +70,7 @@ from the eIDAS Regulation or the amendment proposal:**
 | Attestation Revocation List | A mechanism provided by an Attestation Provider (or a trusted party acting on its behalf) for communicating the revocation or suspension status of attestations, by publishing a list of identifiers of revoked or suspended attestations; and used by a Relying Party to verify the status. \[[Topic 7](../annex-2/annex-2-high-level-requirements.md#a237-topic-7---attestation-validity-checks-and-revocation)\] |
 | Attestation Rulebook | A document describing the attestation type, namespace(s), and other features for a specific attestation type in compliance with the minimum requirements for attestation rulebooks. \[[Topic 12](../annex-2/annex-2-high-level-requirements.md#a2312-topic-12---attestation-rulebooks)\] |
 | Attestation Status List | A mechanism provided by an Attestation Provider (or a trusted party acting on its behalf) for communicating the status of attestations, by publishing status information for all valid attestations at the time of publication. \[[Topic 7](../annex-2/annex-2-high-level-requirements.md#a237-topic-7---attestation-validity-checks-and-revocation)\] |
-| Attestation type | An identifier for a type of attestation, unique within the context of the EUDI Wallet ecosystem. Note: Examples of attestation types are a mobile driving license (mDL), a diploma, or a concert ticket. \[[Topic 12](../annex-2/annex-2-high-level-requirements.md#a2312-topic-12---attestation-rulebooks)\] |
+| Attestation type | An identifier for a type of attestation, unique within the context of the EUDI Wallet ecosystem. Note: Examples of attestation types are a mobile driving licence (mDL), a diploma, or a concert ticket. \[[Topic 12](../annex-2/annex-2-high-level-requirements.md#a2312-topic-12---attestation-rulebooks)\] |
 | Backup and Restore Object | A data structure that includes attributes such as Serial number, Attestation type, Attestation Provider, and Issuance time. \[[Topics 33](../annex-2/annex-2-high-level-requirements.md#a2333-topic-33---eudi-wallet-backup-and-restore), [34](../annex-2/annex-2-high-level-requirements.md#a2334-topic-34---migrate-to-a-different-wallet-solution)\] |
 | Certificate Authority (CA) | An entity which is trusted by one or more parties in the EUDI Wallet ecosystem to create and seal certificates. |
 | Certificate Policy (CP) | Named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. |
@@ -79,7 +79,7 @@ from the eIDAS Regulation or the amendment proposal:**
 | EUDI Wallet Instance | The software installed on a User's device which is part of an EUDI Wallet Solution and belongs to and is controlled by a User. |
 | EUDI Wallet Provider | A public or private organisation, responsible for provisioning and operating an EUDI Wallet Solution. |
 | EUDI Wallet Solution | The product(s) and service(s) provided by an EUDI Wallet Provider to Users. |
-| mDL | Mobile Driving License. \[[Topics 2](../annex-2/annex-2-high-level-requirements.md#a232-topic-2---mobile-driving-license-with-eudi-wallet), [4](../annex-2/annex-2-high-level-requirements.md#a234-topic-4---mdl-rulebook)\] |
+| mDL | Mobile Driving Licence. \[[Topics 2](../annex-2/annex-2-high-level-requirements.md#a232-topic-2---mobile-driving-license-with-eudi-wallet), [4](../annex-2/annex-2-high-level-requirements.md#a234-topic-4---mdl-rulebook)\] |
 | Migration | The activity of moving data from one EUDI Wallet Instance to another EUDI Wallet Instance, where the Wallet Instances are instances of different Wallet Solutions. \[[Topic 34](../annex-2/annex-2-high-level-requirements.md#a2334-topic-34---migrate-to-a-different-wallet-solution)\] |
 | Namespace | A specification of the attribute identifier, syntax and semantics of attributes that can be used in an attestation, having an identifier that is unique within the context of the EUDI Wallet ecosystem. \[[Topic 12](../annex-2/annex-2-high-level-requirements.md#a2312-topic-12---attestation-rulebooks)\] |
 | National Accreditation Bodies (NAB) | A body that performs accreditation with authority derived from a Member State under [Regulation (EC) No 765/2008](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:32008R0765). |

diff --git a/docs/annexes/annex-2/annex-2-high-level-requirements.md b/docs/annexes/annex-2/annex-2-high-level-requirements.md
@@ -86,18 +86,18 @@ identification and authentication of users utilizing their EUDI Wallets.
 | OIA_14 | For both proximity and remote presentation flows, a Relying Party SHALL validate the qualified signature or seal of a PuB-EAA in accordance with [Art.32](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG#d1e2594-73-1) of the eIDAS Regulation. For that verification, the Relying Party SHALL use the public key provided in the qualified certificate of the QTSP supporting the qualified signature or seal. The Relying Party SHALL also validate the qualified certificate of the QTSP using a trust anchor provided in a Trusted List made available in accordance with [Art. 22](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG#d1e2162-73-1) of the eIDAS Regulation. The Relying Party SHALL also verify the certified attributes of the qualified certificate, as specified in [Article 45f](https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32024R1183#d1e3902-1-1). |
 | OIA_15 | For both proximity and remote presentation flows, Relying Parties SHALL validate the signature or seal of a (non-qualified) EAA using a trust anchor provided according to the mechanism(s) specified in the applicable Rulebook, see \[[Topic 12](#a2312-topic-12---attestation-rulebooks)\]. |
 
-#### A.2.3.2 Topic 2 - Mobile Driving License with EUDI Wallet 
+#### A.2.3.2 Topic 2 - Mobile Driving Licence with EUDI Wallet 
 
 *Short description*
 
-A User can obtain from a mobile Driver's License (mDL) Provider and
+A User can obtain from a mobile Driver's Licence (mDL) Provider and
 store in an EUDI Wallet Instance, their mDL. A User can then present the
 mDL to a Relying Party upon request to prove their driving rights
 conveniently, securely, and in compliance with the regulations of all
 Member States.
 
 This Topic contains high-level requirements related to a User presenting
-a mobile Driver's License (mDL) to a Relying Party officer in a
+a mobile Driver's Licence (mDL) to a Relying Party officer in a
 supervised scenario, and also in an unsupervised scenario, in proximity
 offline mode.
 
@@ -138,11 +138,11 @@ For more information, see Annex 3 - \[PID Rulebook\].
 
 *Short description*
 
-The mobile driving license (mDL) Rulebook contains requirements specific
+The mobile driving licence (mDL) Rulebook contains requirements specific
 to the mDL use case within the EUDI Wallet ecosystem.
 
-Mobile driving licenses are legally specified in the proposed EC
-Regulation 2023_127 (4th Driving License Regulation). This Regulation
+Mobile driving licences are legally specified in the proposed EC
+Regulation 2023_127 (4th Driving Licence Regulation). This Regulation
 specifies that mDLs shall comply with the ISO/IEC 18013-5 standard. It
 does not mention any other standards, in particular not \[SD-JWT\].
 Consequently, mDLs issued to a Wallet instance will not be implemented
@@ -643,8 +643,6 @@ C.  Miscellaneous
 
 | **Index** | **Requirement specification** |
 |-----------|-----------------|
-| ACP_07 | During issuance of a (Q)EAA, an Attestation Provider SHALL be able to request the association of the new (Q)EAA to a PID or another (Q)EAA already existing on the Wallet Instance, provided that the Attestation Provider has verified during the issuance process that the new (Q)EAA indeed belongs to the User of that existing PID or (Q)EAA. <p><br>Note: Also see requirement WTE_13 in \[Epic 09\] |
-| ACP_08 | When receiving a combined presentation of attributes, a Relying Party SHOULD NOT refuse any attestation solely because a proof of association between these attestations is absent. |
 | ACP_09 | The common \[ISO18013-5\] and \[OpenID4VP\] protocols SHALL enable a Wallet Instance to transfer a proof of association to a Relying Party. The Commission SHALL take measures to ensure that this is the case. |
 
 #### A.2.3.19 Topic 19 - EUDI Wallet User navigation requirements (Dashboard logs for transparency) 

diff --git a/docs/index.md b/docs/index.md
@@ -69,11 +69,11 @@ see the [tags on this repository](https://github.com/eu-digital-identity-wallet/
 
 See the list of [contributors](https://github.com/eu-digital-identity-wallet/architecture-and-reference-framework/graphs/contributors) who participated in this project.
 
-## License
+## Licence
 
 This project is licensed under the [Attribution 4.0
 International](http://creativecommons.org/licenses/by/4.0/) - see the
-[LICENSE](https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/blob/main/LICENSE) file for details.
+[LICENCE](https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/blob/main/LICENCE) file for details.
 
 ## [European Commission website](https://commission.europa.eu/index_en)