diff --git a/docs/deployment/builders/dockerfiles.md b/docs/deployment/builders/dockerfiles.md
index 66a6adeb8..07aabe090 100644
--- a/docs/deployment/builders/dockerfiles.md
+++ b/docs/deployment/builders/dockerfiles.md
@@ -107,7 +107,7 @@ Dockerfile2
 
 For security reasons - and as per [Docker recommendations](https://github.com/docker/docker/issues/13490) - Dockerfile-based deploys have variables available only during runtime.
 
-For users that require customization in the `build` phase, you may use build arguments via the [docker-options plugin](docs/advanced-usage/docker-options.md):
+For users that require customization in the `build` phase, you may use build arguments via the [docker-options plugin](/docs/advanced-usage/docker-options.md):
 
 ```shell
 dokku docker-options:add node-js-app build '--build-arg NODE_ENV=production'
diff --git a/docs/deployment/logs.md b/docs/deployment/logs.md
index f4f2ce66c..820e5ebd5 100644
--- a/docs/deployment/logs.md
+++ b/docs/deployment/logs.md
@@ -20,7 +20,7 @@ You can easily get logs of an app using the `logs` command:
 dokku logs node-js-app
 ```
 
-Logs are pulled via integration with the scheduler for the specified application via "live tailing". As such, logs from previously running deployments are usually not available. Users that desire to see logs from previous deployments for debugging purposes should persist those logs to external services. Please see Dokku's [vector integration](deployment/logs.md#vector-logging-shipping) for more information on how to persist logs across deployments to ship logs to another service or a third-party platform.
+Logs are pulled via integration with the scheduler for the specified application via "live tailing". As such, logs from previously running deployments are usually not available. Users that desire to see logs from previous deployments for debugging purposes should persist those logs to external services. Please see Dokku's [vector integration](/docs/deployment/logs.md#vector-logging-shipping) for more information on how to persist logs across deployments to ship logs to another service or a third-party platform.
 
 #### Behavioral modifiers
 
diff --git a/docs/deployment/schedulers/docker-local.md b/docs/deployment/schedulers/docker-local.md
index b4f9359d4..ec6e4523b 100644
--- a/docs/deployment/schedulers/docker-local.md
+++ b/docs/deployment/schedulers/docker-local.md
@@ -128,7 +128,7 @@ This plugin implements various functionality through `plugn` triggers to integra
 
 ### Logging support
 
-App logs for the `logs` command are fetched from running containers via the `docker` cli. To persist logs across deployments, consider using Dokku's [vector integration](deployment/logs.md#vector-logging-shipping) to ship logs to another service or a third-party platform.
+App logs for the `logs` command are fetched from running containers via the `docker` cli. To persist logs across deployments, consider using Dokku's [vector integration](/docs/deployment/logs.md#vector-logging-shipping) to ship logs to another service or a third-party platform.
 
 ### Supported Resource Management Properties
 
diff --git a/docs/networking/dns.md b/docs/networking/dns.md
index 78e82ac3f..e675783d6 100644
--- a/docs/networking/dns.md
+++ b/docs/networking/dns.md
@@ -74,4 +74,4 @@ This section is a work in progress.  It is incomplete.
 Using the 'root' of your domain is nearly identical to the previous example.
 
 * hostname is under `example.tld`, still needs `A` record.
-* Update your global domain using the [domains plugin](docs/configuration/domains.md).
+* Update your global domain using the [domains plugin](/docs/configuration/domains.md).
diff --git a/docs/networking/network.md b/docs/networking/network.md
index ae9406da2..237e0e0fe 100644
--- a/docs/networking/network.md
+++ b/docs/networking/network.md
@@ -308,7 +308,7 @@ dokku network:rebuildall
 
 ### Container network interface binding
 
-> This functionality does not control the `--network` docker flag. Please use the [docker-options plugin](docs/advanced-usage/docker-options.md) to manage this flag.
+> This functionality does not control the `--network` docker flag. Please use the [docker-options plugin](/docs/advanced-usage/docker-options.md) to manage this flag.
 
 By default, an app will only bind to the internal interface. This behavior can be modified per app by changing the `bind-all-interfaces` network property.