await in event handler cause immediate rerender

Signed-off-by: jzz <[email protected]>

Author: JZZICK

src/content/learn/queueing-a-series-of-state-updates.md

@@ -63,20 +63,21 @@ But there is one other factor at play here. **React waits until *all* code in th
 
 > **Note:** When using `await` inside an event handler:
 > 
-> - React processes all state updates made before the `await` immediately, 
->   which triggers a rerender before the handler completes.
+> - React processes all state updates made before the `await` immediately,which triggers a rerender
+>   before the handler completes.
 >
-> - This behavior differs from synchronous event handlers, where React 
->   waits until the entire handler finishes.
+> - This behavior differs from synchronous event handlers, where React waits until the entire handler
+>   finishes.
 >
-> - Any state updates after the `await` will be treated as a separate batch, 
->   potentially causing multiple renders.
+> - Any state updates after the `await` will be treated as a separate batch,potentially causing multiple 
+>   renders.
 > 
-> To avoid this behavior, keep all state updates within a single synchronous 
-> batch, or avoid using `await` inside event handlers when possible.
+> To avoid this behavior, keep all state updates within a single synchronous batch, or avoid using `await`
+>  inside event handlers when possible.
 
 ---
 
+
 <Illustration src="/images/docs/illustrations/i_react-batching.png"  alt="An elegant cursor at a restaurant places and order multiple times with React, playing the part of the waiter. After she calls setState() multiple times, the waiter writes down the last one she requested as her final order." />
 
 This lets you update multiple state variables--even from multiple components--without triggering too many [re-renders.](/learn/render-and-commit#re-renders-when-state-updates) But this also means that the UI won't be updated until _after_ your event handler, and any code in it, completes. This behavior, also known as **batching,** makes your React app run much faster. It also avoids dealing with confusing "half-finished" renders where only some of the variables have been updated.

src/content/reference/react/useMemo.md

@@ -1105,7 +1105,7 @@ function ChatRoom({ roomId }) {
     const connection = createConnection(options);
     connection.connect();
     return () => connection.disconnect();
-  }, [options]); // ✅ Only changes when create option changes
+  }, [options]); // ✅ Only changes when createOption changes
   // ...
 ```