diff --git a/website/docs/user_guide/environments.md b/website/docs/user_guide/environments.md
index dd0f1473a9..28cd1ea7bf 100644
--- a/website/docs/user_guide/environments.md
+++ b/website/docs/user_guide/environments.md
@@ -15,7 +15,7 @@ title: Environments
 
 Environments is a new way to organize activation strategy configurations for feature toggles into separate environments. In Unleash, a feature lives across all your environments — after all, the goal is to get the new feature released as soon as possible — but it makes sense to configure the activation differently per environment. You might want the feature enabled for everyone in development, but only for yourself in production, for instance.
 
-Previously, Unleash Enterprise users have been able to leverage [strategy constraints](../advanced/strategy-constraints) to control the rollout across environments. With the new environments feature, this is no longer necessary. Now all activation strategies belong to an explicit environment instead.
+Previously, Unleash Enterprise users have been able to leverage [strategy constraints](https://docs.getunleash.io/advanced/strategy_constraints) to control the rollout across environments. With the new environments feature, this is no longer necessary. Now all activation strategies belong to an explicit environment instead.
 
 Further, connected applications will use environment-scoped API keys to make sure they only download feature toggle configurations for the environment they are running in.