[WAF, DDoS] Update links (#28077)

Author: pedrosousa

src/content/docs/ddos-protection/managed-rulesets/http/http-overrides/configure-dashboard.mdx

@@ -71,7 +71,7 @@ If you cannot deploy any additional overrides, consider editing an existing over
     4. Under **Rule configuration**, select **Browse rules**.
     5. Search for the rules you wish to configure using the available filters. You can search by [tag](/ddos-protection/managed-rulesets/http/rule-categories/) (also known as category).
     6. To configure a single rule, select the desired value for a field in the displayed dropdowns next to the rule.
-        To configure more than one rule, select the rules using the row checkboxes and update the fields for the selected rules using the dropdowns displayed before the table. You can also configure all the rules with a given tag. For more information, refer to [Configure rules in bulk in a managed ruleset](/waf/managed-rules/deploy-zone-dashboard/#configure-rules-in-bulk-in-a-managed-ruleset).
+        To configure more than one rule, select the rules using the row checkboxes and update the fields for the selected rules using the dropdowns displayed before the table. You can also configure all the rules with a given tag. For more information, refer to [Configure a managed ruleset](/waf/managed-rules/deploy-zone-dashboard/#configure-a-managed-ruleset).
     7. Select **Next**.
     </Details>
 

src/content/docs/fundamentals/reference/scans-penetration.mdx

@@ -28,10 +28,10 @@ Targets like `*.cloudflare.com` or other Cloudflare-owned destinations are only
 
 Before starting a penetration test on your [zones](/fundamentals/concepts/accounts-and-zones/#zones), set the following application security configurations for each zone you will run the test on:
 
-1. [Deploy the Cloudflare Managed Ruleset](/waf/managed-rules/deploy-zone-dashboard/#deploy-a-managed-ruleset) and
-   [enable all rules](/waf/managed-rules/deploy-zone-dashboard/#configure-field-values-for-all-the-rules) in the ruleset by setting **Ruleset status** to **Enabled**.
+1. [Deploy the Cloudflare Managed Ruleset](/waf/managed-rules/reference/cloudflare-managed-ruleset/#deploy-in-the-dashboard) and
+   [enable all rules](/waf/managed-rules/reference/cloudflare-managed-ruleset/#ruleset-level-configuration) in the ruleset by setting **Ruleset status** to **Enabled**.
 
-2. [Deploy the Cloudflare OWASP Core Ruleset](/waf/managed-rules/deploy-zone-dashboard/#deploy-a-managed-ruleset) and set the following [ruleset configuration](/waf/managed-rules/deploy-zone-dashboard/#configure-field-values-for-all-the-rules):
+2. [Deploy the Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/configure-dashboard/#deploy-in-the-dashboard) and set the following [ruleset configuration](/waf/managed-rules/reference/owasp-core-ruleset/configure-dashboard/#ruleset-level-configuration):
    - **Paranoia Level**: _PL4_
    - **Score threshold**: _High - 25 and higher_
 

src/content/docs/waf/account/managed-rulesets/deploy-dashboard.mdx

@@ -15,7 +15,7 @@ import { Render, Steps, DashButton } from "~/components";
 This feature requires an Enterprise plan with a paid add-on.
 :::
 
-To deploy a managed ruleset for a single zone, refer to [Deploy a managed ruleset in the dashboard for a zone](/waf/managed-rules/deploy-zone-dashboard/).
+To deploy a managed ruleset for a single zone, refer to [Deploy a WAF managed ruleset in the dashboard](/waf/managed-rules/deploy-zone-dashboard/).
 
 ## Deploy a managed ruleset
 

src/content/docs/waf/get-started.mdx

@@ -77,7 +77,7 @@ If you are testing the WAF against pentesting tools, it is recommended that you
 - **Ruleset action**: _Block_
 - **Ruleset status**: _Enabled_ (enables all rules in the ruleset)
 
-For more information on configuring the Cloudflare Managed Ruleset in the dashboard, refer to [Configure field values for all the rules](/waf/managed-rules/deploy-zone-dashboard/#configure-field-values-for-all-the-rules).
+For more information on configuring the Cloudflare Managed Ruleset in the dashboard, refer to [Cloudflare Managed Ruleset](/waf/managed-rules/reference/cloudflare-managed-ruleset/#configure-in-the-dashboard).
 
 </Details>
 
@@ -177,7 +177,7 @@ Follow one of these strategies to configure the ruleset according to your needs:
 - Start from a strict configuration (paranoia level = _PL4_, score threshold = _Low - 60 and higher_). Reduce the score threshold and paranoia level until you achieve a good false positives/true positives rate for your incoming traffic.
 - Alternatively, start from a more permissive configuration (paranoia level = _PL1_, score threshold = _High - 25 and higher_) and increase both parameters to adjust your protection, trying to keep a low number of false positives.
 
-For more information on configuring the Cloudflare OWASP Core Ruleset in the dashboard, refer to [Configure field values for all the rules](/waf/managed-rules/deploy-zone-dashboard/#configure-field-values-for-all-the-rules).
+For more information on configuring the Cloudflare OWASP Core Ruleset in the dashboard, refer to [Configure in the dashboard](/waf/managed-rules/reference/owasp-core-ruleset/configure-dashboard/#ruleset-level-configuration).
 
 </Details>
 

src/content/docs/waf/managed-rules/reference/owasp-core-ruleset/concepts.mdx

@@ -37,8 +37,8 @@ The available score thresholds are the following:
 - _Medium – 40 and higher_ (default value)
 - _High – 25 and higher_
 
-Each threshold (_Low_, _Medium_, and _High_) has an associated value (_60_, _40_, and _25_, respectively). Configuring a _Low_ threshold means that more rules will have to match the current request for the WAF to apply the configured ruleset action. 
+Each threshold (_Low_, _Medium_, and _High_) has an associated value (_60_, _40_, and _25_, respectively). Configuring a _Low_ threshold means that more rules will have to match the current request for the WAF to apply the configured ruleset action.
 
-When the OWASP Anomaly Score Threshold is set to _High_, file uploads may trigger the `949110: Inbound Anomaly Score Exceeded` rule due to the lower amount of scoring rules needed. Consider adjusting the threshold level, [adjusting individual rules](/waf/managed-rules/deploy-zone-dashboard/#configure-a-single-rule-in-a-managed-ruleset) in the ruleset, or [creating an exception](/waf/managed-rules/waf-exceptions/) if excessive false positives occur.
+When the OWASP Anomaly Score Threshold is set to _High_, file uploads may trigger the `949110: Inbound Anomaly Score Exceeded` rule due to the lower amount of scoring rules needed. Consider [adjusting the score threshold](/waf/managed-rules/reference/owasp-core-ruleset/configure-dashboard/#ruleset-level-configuration), [adjusting individual rules](/waf/managed-rules/reference/owasp-core-ruleset/configure-dashboard/#rule-level-configuration) in the ruleset, or [creating an exception](/waf/managed-rules/waf-exceptions/) if excessive false positives occur.
 
 For an example, refer to [OWASP evaluation example](/waf/managed-rules/reference/owasp-core-ruleset/example/).

src/content/partials/ddos-protection/managed-rulesets/create-override.mdx

@@ -24,7 +24,7 @@ import { Details, Render, Steps, DashButton } from "~/components"
         12. Search for the rules you wish to override using the available filters. You can search for tags.
         13. To override a single rule, select the desired value for a field in the displayed dropdowns next to the rule.
 
-        To configure more than one rule, select the rules using the row checkboxes and update the fields for the selected rules using the dropdowns displayed before the table. You can also configure all the rules with a given tag. For more information, refer to [Configure rules in bulk in a managed ruleset](/waf/managed-rules/deploy-zone-dashboard/#configure-rules-in-bulk-in-a-managed-ruleset).
+        To configure more than one rule, select the rules using the row checkboxes and update the fields for the selected rules using the dropdowns displayed before the table. You can also configure all the rules with a given tag. For more information, refer to [Configure a managed ruleset](/waf/managed-rules/deploy-zone-dashboard/#configure-a-managed-ruleset).
       14. Select **Next**.
       15. Enter a name for your override in **Execution name**.
       </Details>