diff --git a/docs/docs/20-usage/25-multi-pipeline.md b/docs/docs/20-usage/25-multi-pipeline.md
index d798301d8..3773f1f21 100644
--- a/docs/docs/20-usage/25-multi-pipeline.md
+++ b/docs/docs/20-usage/25-multi-pipeline.md
@@ -17,7 +17,7 @@ The Multi-Pipeline feature allows the pipeline to be split into several files an
 ## Example multi-pipeline definition
 :::warning
 Please note that files are only shared between steps of the same pipeline (see [File changes are incremental](/docs/usage/pipeline-syntax#file-changes-are-incremental)). That means you cannot access artifacts e.g. from the `build` pipeline below in the `deploy` pipeline.
-If you still need to pass artifacts between the pipelines you need use storage [plugins](docs/usage/plugins/plugins) (e.g. one which stores files in an Amazon S3 bucket).
+If you still need to pass artifacts between the pipelines you need use storage [plugins](/docs/usage/plugins/plugins) (e.g. one which stores files in an Amazon S3 bucket).
 :::
 
 ```bash
diff --git a/docs/docs/30-administration/10-server-config.md b/docs/docs/30-administration/10-server-config.md
index a5c7eb836..c1fd14cdd 100644
--- a/docs/docs/30-administration/10-server-config.md
+++ b/docs/docs/30-administration/10-server-config.md
@@ -4,7 +4,7 @@
 
 Registration is closed by default. While disabled an administrator needs to add new users manually (exp. `woodpecker-cli user add`).
 
-If registration is open every user with an account at the configured [SCM](docs/administration/vcs/overview) can login to Woodpecker.
+If registration is open every user with an account at the configured [SCM](/docs/administration/vcs/overview) can login to Woodpecker.
 This example enables open registration for users that are members of approved organizations:
 
 ```diff
@@ -338,12 +338,12 @@ Example: `WOODPECKER_LIMIT_CPU_SET=1,2`
 ### `WOODPECKER_CONFIG_SERVICE_ENDPOINT`
 > Default: ``
 
-Specify a configuration service endpoint, see [Configuration Extension](docs/administration/external-configuration-api)
+Specify a configuration service endpoint, see [Configuration Extension](/docs/administration/external-configuration-api)
 
 ### `WOODPECKER_CONFIG_SERVICE_SECRET`
 > Default: ``
 
-Specify a signing secret for the configuration service endpoint, see [Configuration Extension](docs/administration/external-configuration-api)
+Specify a signing secret for the configuration service endpoint, see [Configuration Extension](/docs/administration/external-configuration-api)
 
 ### `WOODPECKER_CONFIG_SERVICE_SECRET_FILE`
 > Default: ``