Update 0_GettingStarted.md

docs/e2e-system-tests/0_GettingStarted.md

@@ -41,15 +41,15 @@ Make sure you have access to the repository using your organization's credential
 
 1. Setting Up Environment Variables for Dev Environment/Cluster:
 
-   - Duplicate the file [devTemplate.env.json](../env_variables/devTemplate.env.json) and rename the duplicated file to `local.env.json` inside the `env_variables` folder.
+   - Duplicate the file [devTemplate.env.json](https://github.com/hpi-schul-cloud/e2e-system-tests/env_variables/devTemplate.env.json) and rename the duplicated file to `local.env.json` inside the `env_variables` folder.
    - Include the required development namespace URLs for BRB/DBC/NBC.
    - Test user data on development clusters are created using the school API.
    - To retrieve the API keys for all three namespaces, navigate to 1Password (1PW).
    - Contact QA team for the necessary 1Password links.
 
 2. Setting Up Environment Variables for Staging Environment/Cluster:
 
-    - Duplicate the file [stagingTemplate.env.json](../env_variables/stagingTemplate.env.json) and rename the duplicated file to `staging.env.json` in the `env_variables` folder.
+    - Duplicate the file [stagingTemplate.env.json](https://github.com/hpi-schul-cloud/e2e-system-tests/env_variables/stagingTemplate.env.json) and rename the duplicated file to `staging.env.json` in the `env_variables` folder.
    - Include the required staging namespace URLs for BRB/DBC/NBC.
    - Test data on the staging environment are fetched from the seed data on the server.
    - Add the environment-specific credentials to `staging.env.json` from 1Password (1PW).