Fix links and update partial (inputParameters >> params)

Author: pedrosousa

src/content/changelogs-next/2025-01-09-rules-overview.mdx

@@ -11,9 +11,10 @@ date: 2025-01-09T11:00:00Z
 ![Rules Overview Interface](~/assets/images/changelog-next/rules/rules-overview.gif)
 
 What you can do:
+
 - **See all your rules in one place** – No more clicking around.
 - **Find rules faster** – Search by name.
 - **Understand execution order** – See how rules run in sequence.
-- **Debug easily** – Use [Trace](/fundamentals/security/trace-request/) without switching tabs.
+- **Debug easily** – Use [Trace](/fundamentals/trace-request/) without switching tabs.
 
 Check it out in [Rules > Overview](https://dash.cloudflare.com/?to=/:account/:zone/rules/overview).

src/content/changelogs/trace.yaml

@@ -1,7 +1,7 @@
 ---
-link: "/fundamentals/security/trace-request/changelog/"
+link: "/fundamentals/trace-request/changelog/"
 productName: Trace
-productLink: "/fundamentals/security/trace-request/"
+productLink: "/fundamentals/trace-request/"
 productArea: Core platform
 productAreaLink: /fundamentals/reference/changelog/platform/
 entries:

src/content/docs/cache/how-to/cache-rules/index.mdx

@@ -30,5 +30,5 @@ The following table describes Cache Rules availability per plan.
 <Render
 	file="troubleshoot-rules-with-trace"
 	product="rules"
-	params={{ one: "Cache Rules" }}
+	params={{ rulesFeatureName: "Cache Rules" }}
 />

src/content/docs/rules/compression-rules/index.mdx

@@ -53,5 +53,5 @@ The following fields are commonly used in expressions of compression rules:
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "compression rules" }}
+	params={{ rulesFeatureName: "compression rules" }}
 />

src/content/docs/rules/configuration-rules/index.mdx

@@ -37,5 +37,5 @@ The number of available configuration rules varies according to your Cloudflare
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "configuration rules" }}
+	params={{ rulesFeatureName: "configuration rules" }}
 />

src/content/docs/rules/origin-rules/index.mdx

@@ -45,4 +45,7 @@ If you override the hostname with an origin rule (via `Host` header override or
 
 Like [Page Rules](/rules/page-rules/), an origin rule performing a `Host` header override will update the SNI value of the original request to the same value of the `Host` header. To set an SNI value different from the `Host` header override, add an SNI override in the same origin rule or create a separate origin rule for this purpose.
 
-<Render file="troubleshoot-rules-with-trace" params={{ one: "origin rules" }} />
+<Render
+	file="troubleshoot-rules-with-trace"
+	params={{ rulesFeatureName: "origin rules" }}
+/>

src/content/docs/rules/transform/index.mdx

@@ -69,5 +69,5 @@ Request and response fields are immutable within each [phase](/ruleset-engine/ab
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "Transform Rules" }}
+	params={{ rulesFeatureName: "Transform Rules" }}
 />

src/content/docs/rules/transform/request-header-modification/index.mdx

@@ -67,5 +67,5 @@ You can create an HTTP request header modification rule [in the dashboard](/rule
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "HTTP request header modification rules" }}
+	params={{ rulesFeatureName: "HTTP request header modification rules" }}
 />

src/content/docs/rules/transform/response-header-modification/index.mdx

@@ -75,5 +75,5 @@ You can create an HTTP response header modification rule [in the dashboard](/rul
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "HTTP response header modification rules" }}
+	params={{ rulesFeatureName: "HTTP response header modification rules" }}
 />

src/content/docs/rules/transform/troubleshooting.mdx

@@ -6,7 +6,6 @@ sidebar:
 head:
   - tag: title
     content: Troubleshoot Transform Rules
-
 ---
 
 When troubleshooting a rule configuration, review the [Transform Rules evaluation](/rules/transform/#transform-rules-evaluation) section to understand how and when your Transform Rule is evaluated for each request.
@@ -17,6 +16,6 @@ For more information on runtime errors related to Transform Rules configuration,
 
 Transform Rules performing request header modifications affect the HTTP headers sent by Cloudflare's network to your origin server. You will not find these headers in your browser request or response data, which can make it difficult to tell if the rule is working as intended.
 
-To check if a request header modification is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/fundamentals/security/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
+To check if a request header modification is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/fundamentals/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
 
 To add HTTP headers that website visitors will receive in their browsers, you must [modify the response headers](/rules/transform/response-header-modification/) instead.