more broken links

Author: patriciasantaana

src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx

@@ -45,7 +45,7 @@ Cloudflare may change the logic of these protection rules from time to time to i
 
 Cloudflare’s network is built to automatically monitor and mitigate large DDoS attacks. Cloudflare also helps mitigate smaller DDoS attacks, based on the following general rules:
 
-- For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by [configuring the HTTP DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/http/configure-dashboard/).
+- For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by [configuring the HTTP DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/http/http-overrides/configure-dashboard/).
 - For zones on Pro, Business, and Enterprise plans, Cloudflare performs an additional check for better detection accuracy: the errors-per-second rate must also be at least five times the normal origin traffic levels before applying DDoS mitigations.
 
 Cloudflare determines the error rate based on all HTTP errors in the 52X range (Internal Server Error) and in the 53X range, except for [error 530](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-530). Currently, for DDoS mitigations based on HTTP error rate, you cannot exclude specific HTTP error codes.
@@ -96,6 +96,6 @@ To configure a rule, refer to the instructions in the following pages:
 For more information on the available configuration parameters, refer to the following pages:
 
 - For the (L7) DDoS protection rules for Origins, User-Agents, and Locations:<br/>
-  [HTTP DDoS Attack Protection parameters](/ddos-protection/managed-rulesets/http/http-overrides/override-parameters/)
+  [HTTP DDoS Attack Protection parameters](/ddos-protection/managed-rulesets/http/override-parameters/)
 - For the (L3/4) DDoS protection rules for Protocols:<br/>
   [Network-layer DDoS Attack Protection parameters](/ddos-protection/managed-rulesets/network/override-parameters/)

src/content/docs/ddos-protection/managed-rulesets/adjust-rules/false-positive.mdx

@@ -37,7 +37,7 @@ Once saved, the rule takes effect within one or two minutes. The rule adjustment
 
 ## Update the adjusted rules later
 
-Later, you can change the [sensitivity level](/ddos-protection/managed-rulesets/network/network-overrides/override-parameters/#sensitivity-level) of the rule causing the false positives to avoid future issues, and change the rule action back to its default value.
+Later, you can change the [sensitivity level](/ddos-protection/managed-rulesets/network/override-parameters/#sensitivity-level) of the rule causing the false positives to avoid future issues, and change the rule action back to its default value.
 
 :::note[Recommendation: Enable DDoS alerts]
 
@@ -48,7 +48,7 @@ Cloudflare recommends that you create notifications for [DDoS alerts](/ddos-prot
 
 ### Avoid false positives while retaining protection and visibility
 
-To see what DDoS Managed Rules do in a high sensitivity level while remaining protected by blocking attacks at a low sensitivity level, Advanced DDoS protection customers can [create a first override](/ddos-protection/managed-rulesets/network/configure-dashboard/#create-a-ddos-override) that blocks attacks at a low sensitivity and a second override to log at a high sensitivity.
+To see what DDoS Managed Rules do in a high sensitivity level while remaining protected by blocking attacks at a low sensitivity level, Advanced DDoS protection customers can [create a first override](/ddos-protection/managed-rulesets/network/network-override/configure-dashboard/#create-a-ddos-override) that blocks attacks at a low sensitivity and a second override to log at a high sensitivity.
 
 The overrides must be set in that order. Otherwise, it will not work. This is because overrides are evaluated in order and will stop at the first override that matches both expression and sensitivity. Setting the overrides in the wrong order would cause the `Log` override at a high sensitivity to match all instances. As a result, Cloudflare will never evaluate the `Block` override that would be placed behind it, causing all rules to be set in `Log` mode.
 

src/content/docs/learning-paths/data-center-protection/post-prefix-fine-tuning.mdx

@@ -13,7 +13,7 @@ On this page, you can find suggestions to monitor your prefix advertisements and
 
 [These rules](/ddos-protection/managed-rulesets/adaptive-protection/) are based on a seven-day rolling window. We recommend reviewing the logs from these adaptive rules in Network Analytics seven days after your last prefix advertisement.
 
-If you see matches for legitimate traffic, consider lowering the sensitivity of the rule and then review the logs again. Once you are satisfied that legitimate traffic is not being flagged, [create a DDoS override](/ddos-protection/managed-rulesets/network/configure-dashboard/#create-a-ddos-override) for this rule with action as `DDOS Dynamic` or `Block`.
+If you see matches for legitimate traffic, consider lowering the sensitivity of the rule and then review the logs again. Once you are satisfied that legitimate traffic is not being flagged, [create a DDoS override](/ddos-protection/managed-rulesets/network/network-overrides/configure-dashboard/#create-a-ddos-override) for this rule with action as `DDOS Dynamic` or `Block`.
 
 ### Advanced TCP Protection and Advanced DNS Protection
 

src/content/docs/learning-paths/data-center-protection/troubleshooting.mdx

@@ -50,7 +50,7 @@ If you suspect that Cloudflare mitigations might be dropping legitimate traffic
 3. In the **All traffic** tab select **Add filter** to configure the filters for the traffic-flow in question — like source IP, destination IP and protocol/ports.
 4. Check the analytics results to determine which Cloudflare mitigation system has dropped the traffic — for example, DDoS Managed Rules, Advanced TCP/DNS Protection or Magic Firewall.
 5. If the traffic was dropped by DDoS Managed Rules:
-	- Check whether the rule that dropped the traffic is customizable. If it is, go to [DDoS Overrides](/ddos-protection/managed-rulesets/network/configure-dashboard/#create-a-ddos-override). There, you can create/amend an existing override to ensure that this endpoint IP is added to the override with a lower sensitivity applied.
+	- Check whether the rule that dropped the traffic is customizable. If it is, go to [DDoS Overrides](/ddos-protection/managed-rulesets/network/network-overrides/configure-dashboard/#create-a-ddos-override). There, you can create/amend an existing override to ensure that this endpoint IP is added to the override with a lower sensitivity applied.
 	- If this rule is not customizable and is part of Cloudflare's always-on standard DDoS mitigations, reach out to Cloudflare support team to request for assistance on this.
 6. If the traffic was dropped by Advanced TCP Protection (ATP):
 	- If the mode for the global rule is **Mitigation** you can set up a filter for `monitoring` so that ATP will not drop traffic for this particular traffic flow.

src/content/docs/ruleset-engine/managed-rulesets/override-managed-ruleset.mdx

@@ -19,8 +19,8 @@ If you are using Terraform, refer to the following pages:
 To define overrides in the Cloudflare dashboard, refer to the following resources:
 
 - [Configure a WAF managed ruleset in the dashboard](/waf/managed-rules/deploy-zone-dashboard/#configure-a-managed-ruleset)
-- [Configure HTTP DDoS Attack Protection in the dashboard](/ddos-protection/managed-rulesets/http/configure-dashboard/)
-- [Configure Network-layer DDoS Attack Protection in the dashboard](/ddos-protection/managed-rulesets/network/configure-dashboard/)
+- [Configure HTTP DDoS Attack Protection in the dashboard](/ddos-protection/managed-rulesets/http/http-overrides/configure-dashboard/)
+- [Configure Network-layer DDoS Attack Protection in the dashboard](/ddos-protection/managed-rulesets/network/network-overrides/configure-dashboard/)
 
 ## Working with overrides
 

src/content/docs/ruleset-engine/reference/phases-list.mdx

@@ -15,7 +15,7 @@ The following tables list the [phases](/ruleset-engine/about/phases/) of Cloudfl
 
 | Phase name       | Used in product/feature                                                                          |
 | ---------------- | ------------------------------------------------------------------------------------------------ |
-| `ddos_l4`        | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/configure-api/) |
+| `ddos_l4`        | [Network-layer DDoS Attack Protection](/ddos-protection/managed-rulesets/network/network-overrides/configure-api/) |
 | `magic_transit`  | [Magic Firewall](/magic-firewall/how-to/add-rules/)                                              |
 | `mt_managed`     | [Magic Firewall managed rulesets](/magic-firewall/how-to/enable-managed-rulesets/)               |
 | `mt_ids_managed` | [Magic Firewall Intrusion Detection System (IDS)](/magic-firewall/about/ids/)                    |

src/content/docs/security/rules.mdx

@@ -45,8 +45,8 @@ The **DDoS Protection** tab shows the multiple DDoS mitigation services provided
 
 To learn more about DDoS protection overrides, refer to the following resources:
 
-- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/override-expressions/)
-- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/override-expressions/)
+- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/http-overrides/override-expressions/)
+- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/network-overrides/override-expressions/)
 
 :::note
 You define overrides for the Network-layer DDoS attack protection managed ruleset at the account level in Account Home > **L3/4 DDoS** > **Network-layer DDoS Protection**.

src/content/docs/security/settings.mdx

@@ -34,8 +34,8 @@ The **DDoS protection** security module shows the multiple DDoS mitigation servi
 
 To learn more about DDoS protection overrides, refer to the following resources:
 
-- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/override-expressions/)
-- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/override-expressions/)
+- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/http-overrides/override-expressions/)
+- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/network-overrides/override-expressions/)
 
 :::note
 You define overrides for the Network-layer DDoS attack protection managed ruleset at the account level in Account Home > **L3/4 DDoS** > **Network-layer DDoS Protection**.

src/content/docs/terraform/additional-configurations/ddos-managed-rulesets.mdx

@@ -21,8 +21,8 @@ DDoS managed rulesets are always enabled. Depending on your Cloudflare services,
 
 If you are using the Cloudflare API, refer to the following resources:
 
-- [Configure HTTP DDoS Attack Protection via API](/ddos-protection/managed-rulesets/http/configure-api/)
-- [Configure Network-layer DDoS Attack Protection via API](/ddos-protection/managed-rulesets/network/configure-api/)
+- [Configure HTTP DDoS Attack Protection via API](/ddos-protection/managed-rulesets/http/http-overrides/configure-api/)
+- [Configure Network-layer DDoS Attack Protection via API](/ddos-protection/managed-rulesets/network/network-overrides/configure-api/)
 
 For more information on deploying and configuring rulesets using the Rulesets API, refer to [Work with managed rulesets](/ruleset-engine/managed-rulesets/) in the Ruleset Engine documentation.
 

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

@@ -8,7 +8,7 @@ import { Details, Render } from "~/components"
 2. Go to Account Home > **L3/4 DDoS** > **Network-layer DDoS Protection**.
 3. Select **Deploy a DDoS override**.
 4. In **Set scope**, specify if you wish to apply the override to all incoming packets or to a subset of the packets.
-5. If you are creating an override for a subset of the incoming packets, define the [custom expression](/ddos-protection/managed-rulesets/network/override-expressions/) that matches the incoming packets you wish to target in the override, using either the Rule Builder or the Expression Editor.
+5. If you are creating an override for a subset of the incoming packets, define the [custom expression](/ddos-protection/managed-rulesets/network/network-overrides/override-expressions/) that matches the incoming packets you wish to target in the override, using either the Rule Builder or the Expression Editor.
 6. Select **Next**.
 7. Depending on what you wish to override, refer to the following sections (you can perform both configurations on the same override):
   <Details header="Configure all the rules in the ruleset (ruleset override)">