diff --git a/src/content/partials/rules/product-execution-order.mdx b/src/content/partials/rules/product-execution-order.mdx
index e0483a4448a187e..a32fb3c1c993d6a 100644
--- a/src/content/partials/rules/product-execution-order.mdx
+++ b/src/content/partials/rules/product-execution-order.mdx
@@ -6,12 +6,16 @@ import { Render } from "~/components";
 
 The execution order of Rules features is the following:
 
-- [Origin Rules](/rules/origin-rules/)
-- [Cache Rules](/cache/how-to/cache-rules/)
-- [Configuration Rules](/rules/configuration-rules/)
 - [Single Redirects](/rules/url-forwarding/single-redirects/)
+- [URL Rewrite Rules](/rules/transform/url-rewrite/)
+- [Configuration Rules](/rules/configuration-rules/)
+- [Origin Rules](/rules/origin-rules/)
 - [Bulk Redirects](/rules/url-forwarding/bulk-redirects/)
+- [Managed Transforms](/rules/transform/managed-transforms/)
+- [Request Header Transform Rules](/rules/transform/request-header-modification/)
+- [Cache Rules](/cache/how-to/cache-rules/)
 - [Snippets](/rules/snippets/)
+- [Cloud Connector](/rules/cloud-connector/)
 
 The different types of rules listed above will take precedence over [Page Rules](/rules/page-rules/). This means that Page Rules will be overridden if there is a match for both Page Rules and the Rules products listed above.
 
diff --git a/src/content/partials/ruleset-engine/rule-terminating-actions.mdx b/src/content/partials/ruleset-engine/rule-terminating-actions.mdx
index 61a242d5f69b605..c86c83507c32722 100644
--- a/src/content/partials/ruleset-engine/rule-terminating-actions.mdx
+++ b/src/content/partials/ruleset-engine/rule-terminating-actions.mdx
@@ -1,8 +1,9 @@
 ---
 {}
-
 ---
 
-Generally speaking, for [non-terminating actions](/ruleset-engine/rules-language/actions/) the last change made by rules in the same [phase](/ruleset-engine/about/phases/) will win (later rules can overwrite changes done by previous rules). However, for terminating actions (*Block*, *Redirect*, or one of the challenge actions), rule evaluation will stop and the action will be executed immediately.
+Generally speaking, for [non-terminating actions](/ruleset-engine/rules-language/actions/) the last change made by rules in the same [phase](/ruleset-engine/about/phases/) will win (later rules can overwrite changes done by previous rules). However, for terminating actions (_Block_, _Redirect_, or one of the challenge actions), rule evaluation will stop and the action will be executed immediately.
+
+For example, if multiple rules with the _Redirect_ action match, Cloudflare will always use the URL redirect of the first rule that matches. Also, if you configure URL redirects using different Cloudflare products (Single Redirects and Bulk Redirects), the product executed first will apply, if there is a rule match (in this case, Single Redirects).
 
-For example, if multiple rules with the *Redirect* action match, Cloudflare will always use the URL redirect of the first rule that matches. Also, if you configure URL redirects using different Cloudflare products (Single Redirects and Bulk Redirects), the product executed first will apply, if there is a rule match (in this case, Single Redirects). Refer to the [Phases list](/ruleset-engine/reference/phases-list/) for the product execution order.
+Refer to the [Phases list](/ruleset-engine/reference/phases-list/) for the product execution order.