diff --git a/content/manuals/compose/how-tos/environment-variables/envvars-precedence.md b/content/manuals/compose/how-tos/environment-variables/envvars-precedence.md
index 832764adf1..9123504ccc 100644
--- a/content/manuals/compose/how-tos/environment-variables/envvars-precedence.md
+++ b/content/manuals/compose/how-tos/environment-variables/envvars-precedence.md
@@ -7,7 +7,7 @@ keywords: compose, environment, env file
 weight: 20
 aliases:
 - /compose/envvars-precedence/
-- /compose/environment-variables/envvvars-precedence/
+- /compose/environment-variables/envvars-precedence/
 ---
 
 When the same environment variable is set in multiple sources, Docker Compose follows a precedence rule to determine the value for that variable in your container's environment.
diff --git a/content/manuals/compose/how-tos/environment-variables/set-environment-variables.md b/content/manuals/compose/how-tos/environment-variables/set-environment-variables.md
index 8269f4f64f..eebce7ad16 100644
--- a/content/manuals/compose/how-tos/environment-variables/set-environment-variables.md
+++ b/content/manuals/compose/how-tos/environment-variables/set-environment-variables.md
@@ -7,7 +7,7 @@ keywords: compose, orchestration, environment, environment variables, container
 aliases:
 - /compose/env/
 - /compose/link-env-deprecated/
-- /compose/set-environment-variables/
+- /compose/environment-variables/set-environment-variables/
 ---
 
 A container's environment is not set until there's an explicit entry in the service configuration to make this happen. With Compose, there are two ways you can set environment variables in your containers with your Compose file.