From c360dbf5368c94c2f4d0e8c1ef0d231a75f41d17 Mon Sep 17 00:00:00 2001
From: Tobias Wilfert <36408720+tobias-wilfert@users.noreply.github.com>
Date: Fri, 3 Oct 2025 14:22:28 +0200
Subject: [PATCH] Fix up sentence structure

---
 .../scrubbing/server-side-scrubbing/index.mdx                   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
index 5a0380720bfa1a..3563fe0ebeec88 100644
--- a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
+++ b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
@@ -95,7 +95,7 @@ To accomodate more fine-grained filtering, the Safe Fields support the same synt
 [Advanced Datascrubbing Sources](/security-legal-pii/scrubbing//advanced-datascrubbing/#sources).
 
 If you want to leave the `user.id` field intact, you can configure the `id` as a Safe Field, but this will also
-mark `extra.id` as a Safe Field. To specifically select the user id, use the full path instead of `user.id`.
+mark `extra.id` as a Safe Field. To specifically select the user id, use the full path `user.id`.
 
 Marking elements of an array as safe requires a wildcard selector, for example `'sys.argv'.*`. A deep wildcard
 can be used to mark all elements contained within an object. The two selectors: `extra.credentials` and