From 1eb593d2a42bde08eeb60dd5ca34786556ff7dab Mon Sep 17 00:00:00 2001
From: Pedro Sousa <680496+pedrosousa@users.noreply.github.com>
Date: Thu, 13 Feb 2025 12:50:28 +0000
Subject: [PATCH] [Ruleset Engine] Update partial

---
 .../docs/ruleset-engine/rules-language/values.mdx    |  4 ++--
 .../rules-language-missing-value-behavior.mdx        | 12 +++++-------
 2 files changed, 7 insertions(+), 9 deletions(-)

diff --git a/src/content/docs/ruleset-engine/rules-language/values.mdx b/src/content/docs/ruleset-engine/rules-language/values.mdx
index 7c403385f58045..7e76a663cacfce 100644
--- a/src/content/docs/ruleset-engine/rules-language/values.mdx
+++ b/src/content/docs/ruleset-engine/rules-language/values.mdx
@@ -146,7 +146,7 @@ It is not possible to define your own arrays. You can only use arrays returned b
 
 <Render
 	file="rules-language-missing-value-behavior"
-	params={{ one: "an out-of-bounds array index" }}
+	params={{ errorDescription: "an out-of-bounds array index" }}
 />
 
 You can only use `[*]` multiple times in the same expression if applied to the same array. Also, you can only use `[*]` in the first argument of a function call.
@@ -217,7 +217,7 @@ It is not possible to define your own maps. You can only use maps returned by fi
 
 <Render
 	file="rules-language-missing-value-behavior"
-	params={{ one: "a non-existing key in a map" }}
+	params={{ errorDescription: "a non-existing key in a map" }}
 />
 
 ## Lists
diff --git a/src/content/partials/ruleset-engine/rules-language-missing-value-behavior.mdx b/src/content/partials/ruleset-engine/rules-language-missing-value-behavior.mdx
index 71939ff1c0a4fa..5adf7c502920ae 100644
--- a/src/content/partials/ruleset-engine/rules-language-missing-value-behavior.mdx
+++ b/src/content/partials/ruleset-engine/rules-language-missing-value-behavior.mdx
@@ -1,11 +1,9 @@
 ---
-inputParameters: errorDescription
-
+params:
+  - errorDescription
 ---
 
-import { Markdown } from "~/components"
-
-Accessing {props.one} produces a "missing value". A missing value has the following behavior:
+Accessing {props.errorDescription} produces a "missing value". A missing value has the following behavior:
 
-* Any comparison `<expr> <op> <literal>` where `<expr>` evaluates to a missing value will evaluate to false.
-* Function calls like `function(<expr>)`, where `<expr>` evaluates to a missing value, will return a missing value in most cases, but the exact behavior can vary per function.
+- Any comparison `<expr> <op> <literal>` where `<expr>` evaluates to a missing value will evaluate to false.
+- Function calls like `function(<expr>)`, where `<expr>` evaluates to a missing value, will return a missing value in most cases, but the exact behavior can vary per function.