diff --git a/documentation/docs/extensibility.md b/documentation/docs/extensibility.md
index 63a9c245e6..be4e5f70c9 100644
--- a/documentation/docs/extensibility.md
+++ b/documentation/docs/extensibility.md
@@ -222,6 +222,6 @@ The provided information should help you understand and extend the functionality
 Since project "Piper" fully builds on [Jenkins Pipelines as Code](https://jenkins.io/doc/book/pipeline-as-code/), you can also go with your own pipeline from scratch in a `Jenkinsfile`.
 
 !!! danger "Decoupling"
-    If you choose this option, you will be decoupled from the innovations provided with project "Piper", unless you re-use stages (as indicated above under [_2. Modified ready-made pipelines_](/extensibility.md#2-modified-ready-made-pipeline)), for example.
+    If you choose this option, you will be decoupled from the innovations provided with project "Piper", unless you re-use stages (as indicated above under [_2. Modified ready-made pipelines_](#2-modified-ready-made-pipeline)), for example.
 
     **We recommend using this only when none of the other provided options suit your use case.**
diff --git a/documentation/docs/steps/isChangeInDevelopment.md b/documentation/docs/steps/isChangeInDevelopment.md
index 1f3282ee9e..81b7a1d84e 100644
--- a/documentation/docs/steps/isChangeInDevelopment.md
+++ b/documentation/docs/steps/isChangeInDevelopment.md
@@ -12,7 +12,7 @@
 
 The target of the status check is a change document identified by an identifier (ID).
 
-Specify the ID by [step parameter](transportRequestUploadSOLMAN#By-Step-Parameter) or [common pipeline environment](transportRequestUploadSOLMAN#Common-Pipeline-Environment).
+Specify the ID by [step parameter](transportRequestUploadSOLMAN.md#By-Step-Parameter) or [common pipeline environment](transportRequestUploadSOLMAN.md#Common-Pipeline-Environment).
 
 ## Return Value
 
diff --git a/documentation/docs/steps/uiVeri5ExecuteTests.md b/documentation/docs/steps/uiVeri5ExecuteTests.md
index 499d64cd25..46c71bc5a5 100644
--- a/documentation/docs/steps/uiVeri5ExecuteTests.md
+++ b/documentation/docs/steps/uiVeri5ExecuteTests.md
@@ -101,7 +101,7 @@ withCredentials([usernamePassword(
 
 There is also the option to use [vault for test credentials](https://www.project-piper.io/infrastructure/vault/#using-vault-for-test-credentials).
 
-In a Pipeline Template, a [Stage Exit](../extensibility/#1-extend-individual-stages) can be used to fetch the credentials and store them in the environment. As the environment is passed down to uiVeri5ExecuteTests, the variables will be present there. This is an example for the stage exit `.pipeline/extensions/Acceptance.groovy` where the `credentialsId` is read from the `config.yml`:
+In a Pipeline Template, a [Stage Exit](../extensibility.md/#1-extend-individual-stages) can be used to fetch the credentials and store them in the environment. As the environment is passed down to uiVeri5ExecuteTests, the variables will be present there. This is an example for the stage exit `.pipeline/extensions/Acceptance.groovy` where the `credentialsId` is read from the `config.yml`:
 
 ```groovy
 void call(Map params) {