From 50693395511f642eac7e58ac202c14272de86c19 Mon Sep 17 00:00:00 2001
From: Luca Forstner <luca.forstner@sentry.io>
Date: Mon, 25 Sep 2023 20:22:00 +0200
Subject: [PATCH] Clarify setContext signature (#7934)

---
 src/platforms/common/enriching-events/context.mdx | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/src/platforms/common/enriching-events/context.mdx b/src/platforms/common/enriching-events/context.mdx
index 765dd78777f89..9a196f5c7f8d7 100644
--- a/src/platforms/common/enriching-events/context.mdx
+++ b/src/platforms/common/enriching-events/context.mdx
@@ -21,7 +21,15 @@ If you need to be able to search on custom data, [use tags](../tags) instead.
 
 ## Structured Context
 
-The best practice to attach custom data is via structured contexts. A context must always be a dictionary or map, and its values can be arbitrary.
+<PlatformSection supported={["javascript", "node"]}>
+  The best way to attach custom data is with a structured context. A context
+  must always be an object and its values can be arbitrary.
+</PlatformSection>
+
+<PlatformSection notSupported={["javascript", "node"]}>
+  The best way to attach custom data is with a structured context. A context
+  must always be an object and its values can be arbitrary.
+</PlatformSection>
 
 <PlatformSection supported={["javascript", "node"]}>