From 79b5d1b1eaff807b701e6847df60aaf371e670e8 Mon Sep 17 00:00:00 2001 From: Open Source Contributor Date: Tue, 21 Apr 2026 19:42:55 -0600 Subject: [PATCH] docs: fix typos in documentation --- src/content/learn/synchronizing-with-effects.md | 2 +- src/content/reference/dev-tools/react-performance-tracks.md | 2 +- .../reference/eslint-plugin-react-hooks/lints/use-memo.md | 2 +- src/content/reference/react-dom/client/createRoot.md | 2 +- src/content/reference/react-dom/client/hydrateRoot.md | 2 +- src/content/reference/react-dom/flushSync.md | 2 +- src/content/reference/react-dom/server/resume.md | 2 +- src/content/reference/react/StrictMode.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/content/learn/synchronizing-with-effects.md b/src/content/learn/synchronizing-with-effects.md index 1eec633882f..6da8e578ecc 100644 --- a/src/content/learn/synchronizing-with-effects.md +++ b/src/content/learn/synchronizing-with-effects.md @@ -607,7 +607,7 @@ A common pitfall for preventing Effects firing twice in development is to use a ```js {1,3-4} const connectionRef = useRef(null); useEffect(() => { - // 🚩 This wont fix the bug!!! + // 🚩 This won't fix the bug!!! if (!connectionRef.current) { connectionRef.current = createConnection(); connectionRef.current.connect(); diff --git a/src/content/reference/dev-tools/react-performance-tracks.md b/src/content/reference/dev-tools/react-performance-tracks.md index d4757b9ec9e..7a876061e52 100644 --- a/src/content/reference/dev-tools/react-performance-tracks.md +++ b/src/content/reference/dev-tools/react-performance-tracks.md @@ -155,5 +155,5 @@ If you await a Promise, React will display duration of that Promise. To see all Different colors are used to indicate the duration of the component render. The darker the color, the longer the duration. -The Server Components track group will always contain a "Primary" track. If React is able to render Server Components concurrently, it will display addititional "Parallel" tracks. +The Server Components track group will always contain a "Primary" track. If React is able to render Server Components concurrently, it will display additional "Parallel" tracks. If more than 8 Server Components are rendered concurrently, React will associate them with the last "Parallel" track instead of adding more tracks. diff --git a/src/content/reference/eslint-plugin-react-hooks/lints/use-memo.md b/src/content/reference/eslint-plugin-react-hooks/lints/use-memo.md index a5a77e5f6e8..56810c35909 100644 --- a/src/content/reference/eslint-plugin-react-hooks/lints/use-memo.md +++ b/src/content/reference/eslint-plugin-react-hooks/lints/use-memo.md @@ -79,7 +79,7 @@ function Component({user}) { } ``` -If the side effect sychronizes React state with some external state (or vice versa), use `useEffect`: +If the side effect synchronizes React state with some external state (or vice versa), use `useEffect`: ```js // ✅ Good: Synchronization in useEffect diff --git a/src/content/reference/react-dom/client/createRoot.md b/src/content/reference/react-dom/client/createRoot.md index c42f2fabfc5..2262af40296 100644 --- a/src/content/reference/react-dom/client/createRoot.md +++ b/src/content/reference/react-dom/client/createRoot.md @@ -419,7 +419,7 @@ const container = document.getElementById("root"); const root = createRoot(container, { // Keep in mind to remove these options in development to leverage // React's default handlers or implement your own overlay for development. - // The handlers are only specfied unconditionally here for demonstration purposes. + // The handlers are only specified unconditionally here for demonstration purposes. onCaughtError: onCaughtErrorProd, onRecoverableError: onRecoverableErrorProd, onUncaughtError: onUncaughtErrorProd, diff --git a/src/content/reference/react-dom/client/hydrateRoot.md b/src/content/reference/react-dom/client/hydrateRoot.md index c48b6eb5196..f015b03277b 100644 --- a/src/content/reference/react-dom/client/hydrateRoot.md +++ b/src/content/reference/react-dom/client/hydrateRoot.md @@ -442,7 +442,7 @@ const container = document.getElementById("root"); hydrateRoot(container, , { // Keep in mind to remove these options in development to leverage // React's default handlers or implement your own overlay for development. - // The handlers are only specfied unconditionally here for demonstration purposes. + // The handlers are only specified unconditionally here for demonstration purposes. onCaughtError: onCaughtErrorProd, onRecoverableError: onRecoverableErrorProd, onUncaughtError: onUncaughtErrorProd, diff --git a/src/content/reference/react-dom/flushSync.md b/src/content/reference/react-dom/flushSync.md index 6fe53337d44..b0019868d8a 100644 --- a/src/content/reference/react-dom/flushSync.md +++ b/src/content/reference/react-dom/flushSync.md @@ -196,7 +196,7 @@ useEffect(() => { }, []); ``` -This will allow the current render to finish and schedule another syncronous render to flush the updates. +This will allow the current render to finish and schedule another synchronous render to flush the updates. diff --git a/src/content/reference/react-dom/server/resume.md b/src/content/reference/react-dom/server/resume.md index ad61f6da561..bd41e4cbf6a 100644 --- a/src/content/reference/react-dom/server/resume.md +++ b/src/content/reference/react-dom/server/resume.md @@ -175,7 +175,7 @@ async function main(frame) { // Layer 2 // Just waiting here for demonstration purposes. // In a real app, the prelude and postponed state would've been serialized in Layer 1 and Layer would deserialize them. - // The prelude content could be flushed immediated as plain HTML while + // The prelude content could be flushed immediately as plain HTML while // React is continuing to render from where the prerender left off. await sleep(2000); diff --git a/src/content/reference/react/StrictMode.md b/src/content/reference/react/StrictMode.md index 16e8d9e6065..d1edaa225e9 100644 --- a/src/content/reference/react/StrictMode.md +++ b/src/content/reference/react/StrictMode.md @@ -1226,7 +1226,7 @@ li { -Now on inital mount in StrictMode, the ref callbacks are all setup, cleaned up, and setup again: +Now on initial mount in StrictMode, the ref callbacks are all setup, cleaned up, and setup again: ``` ...