From f1733883684fb502aa61510741029565a7d85dfd Mon Sep 17 00:00:00 2001
From: Pierre Smeyers <pierre.smeyers@gmail.com>
Date: Sun, 11 Aug 2024 15:19:10 +0200
Subject: [PATCH] docs: update stale links to GitLab docs (anchors)

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index d1585ec..58ae979 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@ This project implements a GitLab CI/CD template to deploy your application with
 
 ## Usage
 
-This template can be used both as a [CI/CD component](https://docs.gitlab.com/ee/ci/components/#use-a-component-in-a-cicd-configuration) 
+This template can be used both as a [CI/CD component](https://docs.gitlab.com/ee/ci/components/#use-a-component) 
 or using the legacy [`include:project`](https://docs.gitlab.com/ee/ci/yaml/index.html#includeproject) syntax.
 
 ### Use as a CI/CD component
@@ -251,7 +251,7 @@ using the appropriate [interpolation syntax](https://docs.docker.com/compose/env
 The Docker Compose template supports two ways of providing your environments url:
 
 * a **static way**: when the environments url can be determined in advance, probably because you're exposing your routes through a DNS you manage,
-* a [**dynamic way**](https://docs.gitlab.com/ee/ci/environments/#set-dynamic-environment-urls-after-a-job-finishes): when the url cannot be known before the
+* a [**dynamic way**](https://docs.gitlab.com/ee/ci/environments/#set-a-dynamic-environment-url): when the url cannot be known before the
   deployment job is executed.
 
 The **static way** can be implemented simply by setting the appropriate configuration variable(s) depending on the environment (see environments configuration chapters):
-- 
GitLab