From 4dd8203222a11d7b3db6bde24e0a2f77be913ffa Mon Sep 17 00:00:00 2001 From: Asko Kauppi Date: Sat, 21 May 2022 13:17:25 +0300 Subject: [PATCH] Typo fix --- src/platforms/common/enriching-events/scopes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/platforms/common/enriching-events/scopes.mdx b/src/platforms/common/enriching-events/scopes.mdx index c7816aa660466e..2cb93bcaddbcc7 100644 --- a/src/platforms/common/enriching-events/scopes.mdx +++ b/src/platforms/common/enriching-events/scopes.mdx @@ -43,7 +43,7 @@ As you start using an SDK, a scope and hub are automatically created for you out of the box. It's unlikely that you'll interact with the hub directly unless you're writing an integration or you want to create or destroy scopes. Scopes, on the other hand are more user facing. You can call `configure-scope` at any point in -time to to modify data stored on the scope. This is useful for doing things like +time to modify data stored on the scope. This is useful for doing things like [modifying the context](../context/).