edits

Author: patriciasantaana

src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix-allowlist.mdx

@@ -13,7 +13,7 @@ import { Render, Steps, DashButton } from "~/components";
 To add an IP address or prefix to the Advanced DDoS Protection [allowlist](/ddos-protection/advanced-ddos-systems/concepts/#allowlist):
 
 <Steps>
-	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
 
 		<DashButton url="/?to=/:account/network-security/ddos" />
 	2. Go to **Advanced Protection**. 

src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx

@@ -13,10 +13,10 @@ import { Steps, DashButton } from "~/components"
 To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to Advanced DDoS Protection:
 
 <Steps>
-	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+  1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
 
-		<DashButton url="/?to=/:account/network-security/ddos" />
-	2. Go to **Advanced Protection**. 
+      <DashButton url="/?to=/:account/network-security/ddos" />
+  2. Go to **Advanced Protection**. 
   3. Under **General settings** > **Prefixes**, select **Edit**.
   4. Expand the **Add existing prefix** section and select **Add** next to the prefix you wish to add.<br/>
     Alternatively, enter a prefix and (optionally) a description in **Prefix** and **Description**, respectively, and select **Add**.

src/content/docs/ddos-protection/advanced-ddos-systems/how-to/create-filter.mdx

@@ -8,7 +8,7 @@ head:
     content: Create a filter for Advanced TCP Protection
 ---
 
-import { GlossaryTooltip, Render, Steps } from "~/components";
+import { GlossaryTooltip, Render, Steps, DashButton } from "~/components";
 
 <Render file="atp-filter-definition" product="ddos-protection" />
 
@@ -24,7 +24,7 @@ To create a [filter](/ddos-protection/advanced-ddos-systems/concepts/#filter) fo
 
 {/* prettier-ignore */}
 <Steps>
-		1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
 
 		<DashButton url="/?to=/:account/network-security/ddos" />
 	2. Go to **Advanced Protection** > **Advanced TCP Protection**.

src/content/docs/ddos-protection/advanced-ddos-systems/how-to/create-rule.mdx

@@ -16,7 +16,7 @@ To create a [SYN flood rule](/ddos-protection/advanced-ddos-systems/overview/adv
 
 {/* prettier-ignore */}
 <Steps>
-	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
 
 		<DashButton url="/?to=/:account/network-security/ddos" />
 
@@ -36,14 +36,17 @@ To create a [SYN flood rule](/ddos-protection/advanced-ddos-systems/overview/adv
 
 {/* prettier-ignore */}
 <Steps>
-1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
-
-	<DashButton url="/?to=/:account/network-security/ddos" />
-2. Go to **Advanced Protection** > **General settings**.
-3. Add the prefixes you wish to onboard. Advanced DNS Protection will only be applied to the prefixes you onboard. If you already onboarded the desired prefixes when you configured Advanced TCP Protection, you do not need to take any other action.
-   :::note
-		Currently, the list of onboarded prefixes is shared with Advanced TCP Protection. Any onboarded prefixes will be subject to both Advanced TCP Protection and Advanced DNS Protection, assuming that your account team has done the initial configuration of both systems. However, you can leave Advanced TCP Protection in monitoring mode.
-	:::
-4. Go to **Advanced DNS Protection**. 5. Select **Create Advanced DNS Protection rule**. 6. In **Mode**, select a mode for the rule. 7. Under **Set scope**, select a [scope](/ddos-protection/advanced-ddos-systems/concepts/#scope) to determine the range of packets that will be affected by the rule. 8. Under **Sensitivity**, define the [burst sensitivity](/ddos-protection/advanced-ddos-systems/concepts/#burst-sensitivity), [rate sensitivity](/ddos-protection/advanced-ddos-systems/concepts/#rate-sensitivity), and [profile sensitivity](/ddos-protection/advanced-ddos-systems/concepts/#profile-sensitivity) to determine when to initiate mitigation. 9. Select **Deploy**.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
 
+		<DashButton url="/?to=/:account/network-security/ddos" />
+	2. Go to **Advanced Protection** > **General settings**.
+	3. Add the prefixes you wish to onboard. Advanced DNS Protection will only be applied to the prefixes you onboard. If you already onboarded the desired prefixes when you configured Advanced TCP Protection, you do not need to take any other action.
+		:::note
+			Currently, the list of onboarded prefixes is shared with Advanced TCP Protection. Any onboarded prefixes will be subject to both Advanced TCP Protection and Advanced DNS Protection, assuming that your account team has done the initial configuration of both systems. However, you can leave Advanced TCP Protection in monitoring mode.
+		:::
+	4. Go to **Advanced DNS Protection**. 
+	5. Select **Create Advanced DNS Protection rule**. 
+	6. In **Mode**, select a mode for the rule. 
+	7. Under **Set scope**, select a [scope](/ddos-protection/advanced-ddos-systems/concepts/#scope) to determine the range of packets that will be affected by the rule. 
+	8. Under **Sensitivity**, define the [burst sensitivity](/ddos-protection/advanced-ddos-systems/concepts/#burst-sensitivity), [rate sensitivity](/ddos-protection/advanced-ddos-systems/concepts/#rate-sensitivity), and [profile sensitivity](/ddos-protection/advanced-ddos-systems/concepts/#profile-sensitivity) to determine when to initiate mitigation. 9. Select **Deploy**.
 </Steps>

src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx

@@ -11,12 +11,12 @@ import { Steps, DashButton } from "~/components"
 To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 
 <Steps>
-1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
-    <DashButton url="/?to=/:account/network-security/ddos" />
-2. Go to **Advanced Protection**.
-3. [Add the prefix](/ddos-protection/advanced-ddos-systems/how-to/add-prefix/) you previously onboarded to Magic Transit to Advanced TCP Protection.
-4. [Add the prefix](/ddos-protection/advanced-ddos-systems/how-to/add-prefix/) (or subset) you wish to exclude as a new, separate prefix in Advanced TCP Protection.
-5. For the prefix you added in the previous step, select **Exclude Subset** in the **Enrolled Prefixes** list.
+  1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
+      <DashButton url="/?to=/:account/network-security/ddos" />
+  2. Go to **Advanced Protection**.
+  3. [Add the prefix](/ddos-protection/advanced-ddos-systems/how-to/add-prefix/) you previously onboarded to Magic Transit to Advanced TCP Protection.
+  4. [Add the prefix](/ddos-protection/advanced-ddos-systems/how-to/add-prefix/) (or subset) you wish to exclude as a new, separate prefix in Advanced TCP Protection.
+  5. For the prefix you added in the previous step, select **Exclude Subset** in the **Enrolled Prefixes** list.
 </Steps>
 
 :::note

src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx

@@ -115,7 +115,7 @@ Optionally, you can create [filters](/ddos-protection/advanced-ddos-systems/conc
 Enable the Advanced DDoS system and begin routing traffic through it.
 
 <Steps>
-	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
 
 		<DashButton url="/?to=/:account/network-security/ddos" />	
 	2. Go to **Advanced Protection** > **General settings**.

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

@@ -5,7 +5,7 @@
 import { Details, Render, Steps } from "~/components"
 
 <Steps>
-  1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+  1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
 
 	<DashButton url="/?to=/:account/network-security/ddos" />
   2. Go to **Network-layer DDoS Protection**.