fix: folder structure by removing the draft folder (#26)

---------

Signed-off-by: jdsika <carlo.van-driesten@vdl.digital>
Signed-off-by: Daniel L. <daniel.liebert@vdl.digital>
Co-authored-by: Daniel L. <daniel.liebert@vdl.digital>

Author: jdsika

EVES/drafts/EVES-001/eves-001.md EVES/EVES-001/eves-001.mdEVES/drafts/EVES-001/eves-001.md renamed to EVES/EVES-001/eves-001.md

@@ -46,7 +46,7 @@ Each EVES must pass through the following stages:
 
 1. **Draft**  
    - Created via a Pull Request (PR).  
-   - Must follow the [EVES template](../../resources/eves-template.md) and meet the requirements in the [Style Guide](../../resources/style-guide.md).  
+   - Must follow the [EVES template](../resources/eves-template.md) and meet the requirements in the [Style Guide](../resources/style-guide.md).  
    - Open for initial community feedback.
 
 2. **Review**:
@@ -171,13 +171,13 @@ This process introduces new clarity regarding EVES stages, references, and roles
 ## 10. References
 
 1. **EVES-004: Roles and Responsibilities of EVES Editors**  
-   [https://github.com/ASCS-eV/EVES/blob/main/drafts/EVES-004/EVES-004.md](../EVES-004/eves-004.md)
+   [../EVES-004/EVES-004.md](../EVES-004/eves-004.md)
 
 2. **RFC 2119: Key Words for Use in RFCs to Indicate Requirement Levels**  
    [https://www.rfc-editor.org/rfc/rfc2119](https://www.rfc-editor.org/rfc/rfc2119)
 
 3. **EVES Template & Style Guide**  
-   [../../resources/](../../resources)
+   [../resources/](../resources)
 
 4. **OpenMSL Governance Rules**  
    [https://openmsl.github.io/doc/OpenMSL/organization/governance_rules.html](https://openmsl.github.io/doc/OpenMSL/organization/governance_rules.html)

EVES/drafts/EVES-002/eves-002.md EVES/EVES-002/eves-002.mdEVES/drafts/EVES-002/eves-002.md renamed to EVES/EVES-002/eves-002.md

@@ -64,7 +64,7 @@ The ENVITED-X Data Space is built on the following core modules:
   - Ensure compliance with the TZIP-21 metadata standard to use open source libraries of the greater Tezos ecosystem.
 - **Key Features**:
   - Whitelisting through the registry contract's "view" entry point.
-  - Minting NFTs representing simulation assets defined in [EVES-003](https://github.com/ASCS-eV/EVES/blob/main/drafts/EVES-003/EVES-003.md).
+  - Minting NFTs representing simulation assets defined in [EVES-003](../EVES-003/eves-003.md).
 - **Standards**:
   - FA2.1 compliance for token creation and ticket-based interoperability.
 
@@ -144,7 +144,7 @@ Future EVES will provide detailed specifications for each module.
 2. [Altme Wallet](https://altme.io)
 3. [Tezos FA2.1 Standard](https://gitlab.com/tzip/tzip/-/blob/master/proposals/tzip-21/tzip-21.md)
 4. [Etherlink Bridge](https://www.etherlinkbridge.com/bridge)
-5. [EVES-003: ENVITED Asset Definition and Upload Process](https://github.com/ASCS-eV/EVES/blob/main/drafts/EVES-003/EVES-003.md)
+5. [EVES-003: ENVITED Asset Definition and Upload Process](../EVES-003/eves-003.md)
 6. [Gaia-X Trust Framework](https://docs.gaia-x.eu/policy-rules-committee/compliance-document/24.11/)
 
 ## Implementation