diff --git a/website/docs/sdks/java.md b/website/docs/sdks/java.md
index 978a92670a..8968113756 100644
--- a/website/docs/sdks/java.md
+++ b/website/docs/sdks/java.md
@@ -57,7 +57,7 @@ Read more about the [Unleash architecture](https://www.unleash-hosted.com/articl
 
 ## Step 4: Provide Unleash Context {#step-4-provide-unleash-context}
 
-It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/control_rollout), which are implemented in the client SDK.
+It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/activation-strategies.md), which are implemented in the client SDK.
 
 The activation strategies is an implementation of rules based on data, which you provide as part of the Unleash Context.
 
diff --git a/website/docs/sdks/php.md b/website/docs/sdks/php.md
index 54f4d45682..cf5d2572f2 100644
--- a/website/docs/sdks/php.md
+++ b/website/docs/sdks/php.md
@@ -56,7 +56,7 @@ Read more about the [Unleash architecture](https://www.unleash-hosted.com/articl
 
 ## Step 4: Provide Unleash Context {#step-4-provide-unleash-context}
 
-It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/control_rollout), which are implemented in the client SDK.
+It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/activation-strategies.md), which are implemented in the client SDK.
 
 The activation strategies is an implementation of rules based on data, which you provide as part of the Unleash Context.
 
diff --git a/website/docs/user_guide/create-feature-toggle.md b/website/docs/user_guide/create-feature-toggle.md
index 119c851919..ffcf4e560e 100644
--- a/website/docs/user_guide/create-feature-toggle.md
+++ b/website/docs/user_guide/create-feature-toggle.md
@@ -32,7 +32,7 @@ The toggle is now created and ready to be used. The toggle does not have any met
 
 ## Step 4: Enable the feature toggle only for your boss! {#step-4-enable-the-feature-toggle-only-for-your-boss}
 
-The next step is to change the activation strategy to only target your boss. You can use the “userWithId”-strategy for that. Using the configuration shown below will only enable the feature toggle for “boss@company.com” and “me@company.com”. Thus, you can safely test your feature in production, without exposing it to your users. In [control roll-out](./control_rollout) with strategies we will go in to greater details on how to use activation strategies to gradually expose new features to your users.
+The next step is to change the activation strategy to only target your boss. You can use the “userIDs”-strategy for that. Using the configuration shown below will only enable the feature toggle for “boss@company.com” and “me@company.com”. Thus, you can safely test your feature in production, without exposing it to your users.
 
 ![Create a feature toggle](/img/create_feature_toggle_userIds.png)