cloudflare
diff --git a/‎src/content/docs/bots/additional-configurations/custom-rules.mdx‎
Lines changed: 5 additions & 5 deletions b/‎src/content/docs/bots/additional-configurations/custom-rules.mdx‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎src/content/docs/waf/feature-interoperability.mdx‎
Lines changed: 9 additions & 2 deletions b/‎src/content/docs/waf/feature-interoperability.mdx‎
Lines changed: 9 additions & 2 deletions
diff --git a/‎src/content/glossary/ruleset-engine.yaml‎
Lines changed: 8 additions & 0 deletions b/‎src/content/glossary/ruleset-engine.yaml‎
Lines changed: 8 additions & 0 deletions
   Settings versus creating WAF custom rules for bot management.
 ---
 
-import { Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components";
 
 Bot protection on Cloudflare works through two complementary mechanisms: built-in settings configured through toggles in **Security Settings**, and [WAF custom rules](/waf/custom-rules/) that you write using [bot management fields](/bots/reference/bot-management-variables/). Understanding when to use each approach helps you avoid creating duplicate rules and simplifies your security configuration.
 
@@ -36,7 +36,7 @@ Custom rules are valuable when you need capabilities that built-in settings do n
 
 Since Bot settings apply to all traffic across your domain, you may need an alternative approach to bot handling for different paths using custom rules — for example, stricter protection on `/login/` than on `/public/`.
 
-#### Example 
+#### Example
 
 Block likely automated traffic only on your login endpoint:
 
@@ -62,7 +62,7 @@ Challenge likely automated traffic only from specific ASNs:
 
 ### Custom actions
 
-Bot settings offer **Block**, **Managed Challenge**, and **Allow** as actions. 
+Bot settings offer **Block**, **Managed Challenge**, and **Allow** as actions.
 
 If you need other actions, such as **Log** (for testing rules before enforcement), **Interactive Challenge**, or **Skip** (to bypass other rules), you need custom rules.
 
@@ -76,6 +76,6 @@ To send bot scores, verified bot status, or JA3/JA4 fingerprints to your origin
 
 ## Execution order
 
-Custom rules execute before Super Bot Fight Mode managed rules. If a custom rule takes a terminating action (such as **Block** or **Managed Challenge**), the request does not reach bot settings. 
+Custom rules execute before Super Bot Fight Mode managed rules. If a custom rule takes a <GlossaryTooltip term="terminating action">terminating action</GlossaryTooltip> (such as _Block_ or _Managed Challenge_), the request does not reach bot settings.
 
-Refer to [Security features interoperability](/waf/feature-interoperability/) for more information.
+Refer to [Security features interoperability](/waf/feature-interoperability/) for more information.
 description: How Cloudflare security features interact and execute in order.
 ---
 
-import { Details, Tabs, TabItem, Steps, DashButton } from "~/components";
+import {
+	Details,
+	Tabs,
+	TabItem,
+	Steps,
+	DashButton,
+	GlossaryTooltip,
+} from "~/components";
 
 Cloudflare applies multiple security features to every incoming request. Each feature runs at a specific stage, and the order determines which feature acts first. Understanding this order helps you avoid conflicts and reduce false positives.
 
 ## Execution order
 
-Cloudflare security features powered by the [Ruleset Engine](/ruleset-engine/) run in a fixed sequence of phases. When a request arrives, it passes through each phase in order. If a rule takes a [terminating action](/ruleset-engine/rules-language/actions/) (for example, _Block_ or _Managed Challenge_), the request stops and does not reach later phases.
+Cloudflare security features powered by the [Ruleset Engine](/ruleset-engine/) run in a fixed sequence of phases. When a request arrives, it passes through each phase in order. If a rule takes a <GlossaryTooltip term="terminating action" link="/ruleset-engine/rules-language/actions/">terminating action</GlossaryTooltip> (for example, _Block_ or _Managed Challenge_), the request stops and does not reach later phases.
 
 The security-related request phases, in execution order, are:
 
 
+---
+productName: Ruleset Engine
+entries:
+  - term: terminating action
+    general_definition: |-
+      a rule action like _Block_ that stops the evaluation of remaining rules.
+    associated_products:
+      - WAF