diff --git a/src/content/docs/ruleset-engine/rules-language/actions.mdx b/src/content/docs/ruleset-engine/rules-language/actions.mdx
index 88e5aeb2670a0e5..f2477f19955369b 100644
--- a/src/content/docs/ruleset-engine/rules-language/actions.mdx
+++ b/src/content/docs/ruleset-engine/rules-language/actions.mdx
@@ -16,12 +16,11 @@ The action of a rule tells Cloudflare how to handle matches for the rule [expres
 
 The table below lists the actions available in the Rules language.
 
-Some actions like *Block*, called terminating actions, will stop the evaluation of the remaining rules. The *Skip* action will skip the evaluation of *some* rules when there is a match, but the exact behavior will depend on the rule configuration.
+Some actions like _Block_, called terminating actions, will stop the evaluation of the remaining rules. The _Skip_ action will skip the evaluation of _some_ rules when there is a match, but the exact behavior will depend on the rule configuration.
 
 The available actions depend on the [phase](/ruleset-engine/about/phases/) where you are configuring the rule. Refer to each product’s documentation for details on the phase(s) supported by that product.
 
-
-
+{/* prettier-ignore */}
 <table style="width: 100%">
   <thead>
     <tr>
@@ -124,6 +123,12 @@ The available actions depend on the [phase](/ruleset-engine/about/phases/) where
           The available skip options depend on the phase where you configure the rule. Refer to each
           product’s documentation for details.
         </p>
+        <p>
+          If you configure a rule with the <em>Skip</em> action at the account level it will only
+          affect rules/phases configured at the account level, not at the zone level.
+          To skip rules/phases at the zone level you must configure a rule with the <em>Skip</em>
+          action at the zone level.
+        </p>
       </td>
       <td>
         No
@@ -283,9 +288,6 @@ The available actions depend on the [phase](/ruleset-engine/about/phases/) where
   </tbody>
 </table>
 
-
-
 :::note
-
-Cloudflare Firewall Rules, now deprecated, supports a different set of actions, including the *Allow* and *Bypass* actions. Refer to [Firewall rules actions](/firewall/cf-firewall-rules/actions/) for more information.
+Cloudflare Firewall Rules, now deprecated, supports a different set of actions, including the _Allow_ and _Bypass_ actions. Refer to [Firewall rules actions](/firewall/cf-firewall-rules/actions/) for more information.
 :::
diff --git a/src/content/docs/waf/custom-rules/skip/options.mdx b/src/content/docs/waf/custom-rules/skip/options.mdx
index 97de64c7cd9d0a6..7123c837cda991f 100644
--- a/src/content/docs/waf/custom-rules/skip/options.mdx
+++ b/src/content/docs/waf/custom-rules/skip/options.mdx
@@ -46,10 +46,12 @@ The available skip options in custom rules are the following:
     | [Rate Limiting (previous version)](/waf/reference/legacy/old-rate-limiting/)         | `rateLimit`     |
     | [WAF managed rules (previous version)](/waf/reference/legacy/old-waf-managed-rules/) | `waf`           |
 
-  - The API values are case sensitive.
+  - The API values are case-sensitive.
+
+  - Currently, you cannot skip [Bot Fight Mode](/bots/get-started/free/), only Super Bot Fight Mode (refer to Skip phases above).
 
 :::note
-Currently, you cannot skip [Bot Fight Mode](/bots/get-started/free/), only Super Bot Fight Mode (refer to Skip phases above).
+If you configure a skip rule at the account level it will only affect other rules/phases configured at the account level, not at the zone level. To skip rules/phases at the zone level you must configure a skip rule at the zone level.
 :::
 
 ## Logging