Ruleset Engine - Remove availability notice from every page (#1749)

Author: pedrosousa

products/firewall/src/content/cf-rulesets/common-use-cases/deploy-cmr-joomla-only.md

@@ -7,12 +7,6 @@ order: 772
 
 # Use category overrides to enable Joomla rules
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 Use the [Rulesets API](/cf-rulesets/rulesets-api) to deploy Managed Rulesets and override their behavior. This ensures that **only rules with a specific tag are enabled**. By default, enabled rules run with actions set by the ruleset issuer in the Managed Ruleset.
 
 Follow the steps below to deploy Managed Rulesets that enable rules tagged with `joomla`.

products/firewall/src/content/cf-rulesets/common-use-cases/deploy-cmr-wordpress-block.md

@@ -7,12 +7,6 @@ order: 771
 
 # Use tag overrides to set WordPress rules to Block
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 Follow the steps below to deploy a Managed Ruleset and override rules for a specific tag.
 
 1. [Add a rule](/cf-rulesets/deploy-rulesets) to a phase to deploy a Managed Ruleset.

products/firewall/src/content/cf-rulesets/common-use-cases/enable-selected-rules.md

@@ -7,12 +7,6 @@ order: 773
 
 # Use rulesets and rule overrides to only enable selected rules
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 Use a ruleset override and a rule override in the ruleset of a phase to deploy selected rules in a Managed Ruleset.
 
 1. [Add a rule](/cf-rulesets/deploy-rulesets) to the ruleset of a phase to deploy a Managed Ruleset.

products/firewall/src/content/cf-rulesets/common-use-cases/index.md

@@ -7,12 +7,6 @@ order: 770
 
 # Workflow examples
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 You cannot edit Managed Rulesets, but you can add overrides to Managed Rulesets deployed to a phase. Overrides take precedence over the default behavior of the Managed Ruleset.
 
 For more information on overriding Managed Rulesets, see [Override a Managed Ruleset](/cf-rulesets/managed-rulesets/override-managed-ruleset/).

products/firewall/src/content/cf-rulesets/common-use-cases/override-ddos-rule-sensitivity.md

@@ -6,12 +6,6 @@ order: 775
 
 # Adjust the sensitivity of a specific HTTP DDoS rule to Low
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 Follow the steps below to override the sensitivity of a specific rule of the Cloudflare HTTP DDoS Managed Ruleset.
 
 1. [Add a rule](/cf-rulesets/deploy-rulesets) to a phase to deploy the Cloudflare HTTP DDoS Managed Ruleset. You only need to deploy this specific ruleset when you wish to define one or more overrides, since it is enabled by default.

products/firewall/src/content/cf-rulesets/common-use-cases/override-ruleset-tag-rule.md

@@ -7,12 +7,6 @@ order: 774
 
 # Deploy a Managed Ruleset with ruleset, tag, and rule overrides
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 Customize the deployment of Managed Rulesets with a combination of ruleset overrides, tag overrides, and rule overrides in your root ruleset.
 
 1. [Add a rule](/cf-rulesets/deploy-rulesets) to a phase to deploy a Managed Ruleset.

products/firewall/src/content/cf-rulesets/create-phase-rulesets.md

@@ -7,12 +7,6 @@ order: 720
 
 # Create phase rulesets
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 A phase behaves like a ruleset. You must create the ruleset for a phase to be able to add rules and deploy rulesets to it.
 
 Use the [Rulesets API](/cf-rulesets/rulesets-api) to create a phase ruleset. You can create a phase ruleset at the account level or at the zone level.

products/firewall/src/content/cf-rulesets/custom-rulesets/add-rules-ruleset.md

@@ -7,12 +7,6 @@ order: 762
 
 # Add rules to a custom ruleset
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 To add rules to an existing custom ruleset, execute a `PUT` request to the custom ruleset and pass the rules in an array. Each rule contains an expression and action.
 
 <Aside type='info' header='Info'>

products/firewall/src/content/cf-rulesets/custom-rulesets/create-custom-ruleset.md

@@ -7,12 +7,6 @@ order: 761
 
 # Create a custom ruleset
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 The following `POST` request creates a new custom ruleset. Set the `kind` field to `custom` and specify the name of the phase where you want to create the custom ruleset in the `phase` field.
 
 ```json

products/firewall/src/content/cf-rulesets/custom-rulesets/deploy-custom-ruleset.md

@@ -7,12 +7,6 @@ order: 763
 
 # Deploy a custom ruleset
 
-<Aside type='warning' header='Important'>
-
-This feature is part of an early access experience for selected customers.
-
-</Aside>
-
 Before you begin:
 
 1. Obtain the name of the phase where you want to deploy the custom ruleset.