From 4d4495008dbd5b97901c514c6267a54bc9b78c5d Mon Sep 17 00:00:00 2001
From: Sandesh  Pyakurel <82999440+Sandesh-Pyakurel@users.noreply.github.com>
Date: Fri, 13 Oct 2023 12:20:26 +0545
Subject: [PATCH] Fix: typo in context.md file (#680)

* Typo fixed in context.md file

* README.md generated
---
 README.md                             | 2 +-
 docs/basic/getting-started/context.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index fa1b9f62..7d989024 100644
--- a/README.md
+++ b/README.md
@@ -1532,7 +1532,7 @@ const MyComponent = () => {
 };
 ```
 
-However, it would be preferrable to not have to check for `null`, since we know that the context won't be `null`. One way to do that is to provide a custom hook to use the context, where an error is thrown if the context is not provided:
+However, it would be preferable to not have to check for `null`, since we know that the context won't be `null`. One way to do that is to provide a custom hook to use the context, where an error is thrown if the context is not provided:
 
 ```tsx
 import { createContext } from "react";
diff --git a/docs/basic/getting-started/context.md b/docs/basic/getting-started/context.md
index df19d8fc..964a12ba 100644
--- a/docs/basic/getting-started/context.md
+++ b/docs/basic/getting-started/context.md
@@ -83,7 +83,7 @@ const MyComponent = () => {
 };
 ```
 
-However, it would be preferrable to not have to check for `null`, since we know that the context won't be `null`. One way to do that is to provide a custom hook to use the context, where an error is thrown if the context is not provided:
+However, it would be preferable to not have to check for `null`, since we know that the context won't be `null`. One way to do that is to provide a custom hook to use the context, where an error is thrown if the context is not provided:
 
 ```tsx
 import { createContext } from "react";