From 0af6f20c77c209a5ea5691f2d1c15e0e359fbed6 Mon Sep 17 00:00:00 2001
From: henrykrinkle01 <162001892+henrykrinkle01@users.noreply.github.com>
Date: Tue, 18 Mar 2025 17:54:32 +0700
Subject: [PATCH] Fix grammar (#15533)

---
 documentation/docs/06-runtime/02-context.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/docs/06-runtime/02-context.md b/documentation/docs/06-runtime/02-context.md
index 30799215b6..87b93a92b2 100644
--- a/documentation/docs/06-runtime/02-context.md
+++ b/documentation/docs/06-runtime/02-context.md
@@ -30,7 +30,7 @@ export const myGlobalState = $state({
 This has a few drawbacks though:
 
 - it only safely works when your global state is only used client-side - for example, when you're building a single page application that does not render any of your components on the server. If your state ends up being managed and updated on the server, it could end up being shared between sessions and/or users, causing bugs
-- it may give the false impression that certain state is global when in reality it should only used in a certain part of your app
+- it may give the false impression that certain state is global when in reality it should only be used in a certain part of your app
 
 To solve these drawbacks, Svelte provides a few `context` primitives which alleviate these problems.