From 9a0c12c860a4cd73cd53f8c3130e889026801d0b Mon Sep 17 00:00:00 2001 From: Pedro Sousa <680496+pedrosousa@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:07:15 +0000 Subject: [PATCH] [Rules] Update link --- src/content/docs/rules/transform/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/rules/transform/index.mdx b/src/content/docs/rules/transform/index.mdx index cbac5dbdd7fc2e4..4c79246ab40b5d3 100644 --- a/src/content/docs/rules/transform/index.mdx +++ b/src/content/docs/rules/transform/index.mdx @@ -58,7 +58,7 @@ Managed Transforms run before other types of Transform Rules that modify HTTP he Transform Rules run in order. Rules that appear later in the list of Transform Rules can overwrite changes done by previous rules. You can define the rule order in the dashboard or via API. -Request and response fields are immutable within each [phase](/ruleset-engine/about/phases/) while evaluating Transform Rules for a request/response. For more information, refer to [Rule evaluation and field values](/ruleset-engine/about/rules/#rule-evaluation). +Request and response fields are immutable within each [phase](/ruleset-engine/about/phases/) while evaluating Transform Rules for a request/response. For more information, refer to [Field values during rule evaluation](/ruleset-engine/about/rules/#field-values-during-rule-evaluation).