network override

Author: patriciasantaana

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

@@ -45,30 +45,31 @@ If you cannot deploy any additional overrides, consider editing an existing over
 
 ### Create a DDoS override
 
+<Steps>
 1. Enter a descriptive name for the override in **Override name**.
 2. If you are an Enterprise customer with the Advanced DDoS Protection subscription:
-   1. Under **Override scope**, review the scope of the override — by default, all incoming requests for the current zone.
-   2. If necessary, select **Edit scope** and configure the [custom filter expression](/ddos-protection/managed-rulesets/http/http-overrides/override-expressions/) that will determine the override scope.
+    1. Under **Override scope**, review the scope of the override — by default, all incoming requests for the current zone.
+    2. If necessary, select **Edit scope** and configure the [custom filter expression](/ddos-protection/managed-rulesets/http/http-overrides/override-expressions/) that will determine the override scope.
 3. 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)">
-  4. To always apply a given action for all the rules in the ruleset, select an action in **Ruleset action**.
-  5. To set the sensitivity level for all the rules in the ruleset, select a value in **Ruleset sensitivity**.
-  </Details>
+    <Details header="Configure all the rules in the ruleset (ruleset override)">
+    4. To always apply a given action for all the rules in the ruleset, select an action in **Ruleset action**.
+    5. To set the sensitivity level for all the rules in the ruleset, select a value in **Ruleset sensitivity**.
+    </Details>
 
-  <Details header="Configure one or more rules">
-  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).
-  7. Select **Next**.
-  </Details>
+    <Details header="Configure one or more rules">
+    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).
+    7. Select **Next**.
+    </Details>
 
-  :::note[Notes]
+    :::note[Notes]
 
-  - Tag and rule overrides have priority over ruleset overrides.
-  - <Render file="managed-rulesets/read-only-rules-note" />
-  :::
+    - Tag and rule overrides have priority over ruleset overrides.
+    - <Render file="managed-rulesets/read-only-rules-note" />
+    :::
 
 4. Select **Save**.
-
+</Steps>
 <Render file="managed-rulesets/delete-override" params={{ one: "select your account and domain", two: "Security > DDoS" }} />

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

@@ -2,35 +2,35 @@
 {}
 ---
 
-import { Details, Render } from "~/components"
+import { Details, Render, Steps } from "~/components"
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-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/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)">
-  8. Select **Next**.
-  9. Enter a name for your override in **Execution name**.
-  10. To always apply a given action for all the rules in the ruleset, select an action in **Ruleset action**.
-  11. To set the sensitivity level for all the rules in the ruleset, select a value in **Ruleset sensitivity**.
-  </Details>
+<Steps>
+  1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+  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/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)">
+        8. Select **Next**.
+        9. Enter a name for your override in **Execution name**.
+        10. To always apply a given action for all the rules in the ruleset, select an action in **Ruleset action**.
+        11. To set the sensitivity level for all the rules in the ruleset, select a value in **Ruleset sensitivity**.
+      </Details>
+      <Details header="Configure one or more rules">
+        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.
 
-  <Details header="Configure one or more rules">
-  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).
+      14. Select **Next**.
+      15. Enter a name for your override in **Execution name**.
+      </Details>
 
-      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).
-  14. Select **Next**.
-  15. Enter a name for your override in **Execution name**.
-  </Details>
+      :::note[Notes]
 
-  :::note[Notes]
-
-  - Tag and rule overrides have priority over ruleset overrides.
-  - <Render file="managed-rulesets/read-only-rules-note" product="ddos-protection" />
-  :::
-
-8. To save and deploy the override, select **Deploy**. If you are not ready to deploy your override, select **Save as Draft**.
+      - Tag and rule overrides have priority over ruleset overrides.
+      - <Render file="managed-rulesets/read-only-rules-note" product="ddos-protection" />
+      :::
+  8. To save and deploy the override, select **Deploy**. If you are not ready to deploy your override, select **Save as Draft**.
+</Steps>