docs: fix some typos (#2483)

Signed-off-by: frameflare <[email protected]>
pmndrs · Apr 5, 2024 · 1049ae1 · 1049ae1
1 parent 11a798b
commit 1049ae1
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/docs/extensions/effect.mdx b/docs/extensions/effect.mdx
@@ -97,7 +97,7 @@ function MyComponent() {
 
  </details>
 
-- **Resistent To Infinite Loops:**
+- **Resistant To Infinite Loops:**
  `atomEffect` does not rerun when it changes a value with `set` that it is watching.
 
  <!-- prettier-ignore -->
@@ -370,7 +370,7 @@ This guarantees that a single effect will be used regardless of how many calls t
 
 The same guarantee can be achieved with the useEffect hook if you ensure that the useEffect is idempotent.
 
-atomEffects are distinguished from useEffect in a few other ways. They can directly react to atom state changes, are resistent to infinite loops, and can be mounted conditionally.
+atomEffects are distinguished from useEffect in a few other ways. They can directly react to atom state changes, are resistant to infinite loops, and can be mounted conditionally.
 
 #### It's up to you
 

diff --git a/docs/guides/migrating-to-v2-api.mdx b/docs/guides/migrating-to-v2-api.mdx
@@ -231,7 +231,7 @@ const splittedAtom = splitAtom(unwrap(asyncArrayAtom, () => []))
 ```
 
 As of writing, `unwrap` is unstable and not documented.
-You can instead use `loadable`, which gives more controll on loading status.
+You can instead use `loadable`, which gives more control on loading status.
 If you need to use `<Suspense>`, atoms-in-atom pattern would help.
 
 For more information, refer the following discussions:

diff --git a/docs/utilities/storage.mdx b/docs/utilities/storage.mdx
@@ -1,7 +1,7 @@
 ---
 title: Storage
 nav: 3.01
-keywords: storage,localstorage,sessionstorage,asyncstorage,persist,persistance
+keywords: storage,localstorage,sessionstorage,asyncstorage,persist,persistence
 ---
 
 ## atomWithStorage