diff --git a/_snippets/integrations/builtin/core-nodes/code-node.md b/_snippets/integrations/builtin/core-nodes/code-node.md
index 2b2c0f59158..9475427de2a 100644
--- a/_snippets/integrations/builtin/core-nodes/code-node.md
+++ b/_snippets/integrations/builtin/core-nodes/code-node.md
@@ -39,7 +39,7 @@ The Code node supports:
 
 ### External libraries
 
-If you self-host n8n, you can import and use built-in and external npm modules in the Code node. To learn how to enable external modules, refer to the [Configuration Environment Variables](/hosting/configuration/environment-variables/) guide.
+If you self-host n8n, you can import and use built-in and external npm modules in the Code node. To learn how to enable external modules, refer to the [Enable modules in Code node](/hosting/configuration/configuration-examples/modules-in-code-node/) guide.
 
 If you use n8n Cloud, you can't import external npm modules. n8n makes two modules available for you:
 
diff --git a/docs/hosting/installation/server-setups/aws.md b/docs/hosting/installation/server-setups/aws.md
index 1ddcd763c44..4896bc848e8 100644
--- a/docs/hosting/installation/server-setups/aws.md
+++ b/docs/hosting/installation/server-setups/aws.md
@@ -80,7 +80,7 @@ The `postgres-deployment.yaml` manifest then uses the values from this manifest
 
 ### Create a volume for file storage
 
-While not essential for running n8n, using persistent volumes helps maintain files uploaded while using n8n and if you want to persist [manual n8n encryption keys](/hosting/configuration/environment-variables/) between restarts, which saves a file containing the key into file storage during startup.
+While not essential for running n8n, using persistent volumes helps maintain files uploaded while using n8n and if you want to persist [manual n8n encryption keys](/hosting/configuration/environment-variables/deployment/) between restarts, which saves a file containing the key into file storage during startup.
 
 The `n8n-claim0-persistentvolumeclaim.yaml` manifest creates this, and the n8n Deployment mounts that claim in the `volumes` section of the `n8n-deployment.yaml` manifest.
 
diff --git a/docs/hosting/installation/server-setups/azure.md b/docs/hosting/installation/server-setups/azure.md
index 620723d38c8..defb492f10f 100644
--- a/docs/hosting/installation/server-setups/azure.md
+++ b/docs/hosting/installation/server-setups/azure.md
@@ -78,7 +78,7 @@ The `postgres-deployment.yaml` manifest then uses the values from this manifest
 While not essential for running n8n, using persistent volumes is required for:
 
 * Using nodes that interact with files, such as the binary data node.
-* If you want to persist [manual n8n encryption keys](/hosting/configuration/environment-variables/) between restarts. This saves a file containing the key into file storage during startup.
+* If you want to persist [manual n8n encryption keys](/hosting/configuration/environment-variables/deployment/) between restarts. This saves a file containing the key into file storage during startup.
 
 The `n8n-claim0-persistentvolumeclaim.yaml` manifest creates this, and the n8n Deployment mounts that claim in the `volumes` section of the `n8n-deployment.yaml` manifest.
 
diff --git a/docs/hosting/installation/server-setups/google-cloud.md b/docs/hosting/installation/server-setups/google-cloud.md
index 5a107a22609..3d135b250a5 100644
--- a/docs/hosting/installation/server-setups/google-cloud.md
+++ b/docs/hosting/installation/server-setups/google-cloud.md
@@ -90,7 +90,7 @@ The `postgres-deployment.yaml` manifest then uses the values from this manifest
 While not essential for running n8n, using persistent volumes is required for:
 
 * Using nodes that interact with files, such as the binary data node.
-* If you want to persist [manual n8n encryption keys](/hosting/configuration/environment-variables/) between restarts. This saves a file containing the key into file storage during startup.
+* If you want to persist [manual n8n encryption keys](/hosting/configuration/environment-variables/deployment/) between restarts. This saves a file containing the key into file storage during startup.
 
 The `n8n-claim0-persistentvolumeclaim.yaml` manifest creates this, and the n8n Deployment mounts that claim in the `volumes` section of the `n8n-deployment.yaml` manifest.
 
diff --git a/docs/hosting/installation/server-setups/heroku.md b/docs/hosting/installation/server-setups/heroku.md
index 31085f51437..19a3a63bb25 100644
--- a/docs/hosting/installation/server-setups/heroku.md
+++ b/docs/hosting/installation/server-setups/heroku.md
@@ -30,7 +30,7 @@ Heroku pre-fills the configuration options defined in the `env` section of the `
 
 You can change any of these values to suit your needs. You must change the following values:
 
-- **N8N_ENCRYPTION_KEY**, which n8n uses to [encrypt user account details](/hosting/configuration/environment-variables/) before saving to the database.
+- **N8N_ENCRYPTION_KEY**, which n8n uses to [encrypt user account details](/hosting/configuration/environment-variables/deployment/) before saving to the database.
 - **WEBHOOK_URL** should match the application name you create to ensure that webhooks have the correct URL.
 
 ### Deploy n8n