From 5b2d697a2cf5be297e2188b64f6730ba869b290a Mon Sep 17 00:00:00 2001 From: bb8dd Date: Tue, 21 Feb 2023 23:30:20 +0900 Subject: [PATCH] fix typo --- beta/src/content/reference/react/useReducer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/beta/src/content/reference/react/useReducer.md b/beta/src/content/reference/react/useReducer.md index 70c0b5a69bf..574da648c90 100644 --- a/beta/src/content/reference/react/useReducer.md +++ b/beta/src/content/reference/react/useReducer.md @@ -84,7 +84,7 @@ React will set the next state to the result of calling the `reducer` function yo * If the new value you provide is identical to the current `state`, as determined by an [`Object.is`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/is) comparison, React will **skip re-rendering the component and its children.** This is an optimization. React may still need to call your component before ignoring the result, but it shouldn't affect your code. -* React [batches state updates.](/learn/queueing-a-series-of-state-updates) It updates the screen **after all the event handlers have run** and have called their `set` functions. This prevents multiple re-renders during a single event. In the rare case that you need to force React to update the screen earlier, for example to access the DOM, you can use [`flushSync`.](/reference/react-dom/flushsync) +* React [batches state updates.](/learn/queueing-a-series-of-state-updates) It updates the screen **after all the event handlers have run** and have called their `set` functions. This prevents multiple re-renders during a single event. In the rare case that you need to force React to update the screen earlier, for example to access the DOM, you can use [`flushSync`.](/reference/react-dom/flushSync) ---