From d4e42ab21f0cc7d8b79d1a619654e27c79e10af6 Mon Sep 17 00:00:00 2001 From: Beau House <58791971+beau-house@users.noreply.github.com> Date: Thu, 2 Feb 2023 15:29:40 -0800 Subject: [PATCH] Add missing word (#5537) --- beta/src/content/reference/react/useMemo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/beta/src/content/reference/react/useMemo.md b/beta/src/content/reference/react/useMemo.md index 754e79da..b2b3dafe 100644 --- a/beta/src/content/reference/react/useMemo.md +++ b/beta/src/content/reference/react/useMemo.md @@ -633,7 +633,7 @@ A JSX node like `` is an object like `{ type: List, However, if React sees the same exact JSX as during the previous render, it won't try to re-render your component. This is because JSX nodes are [immutable.](https://en.wikipedia.org/wiki/Immutable_object) A JSX node object could not have changed over time, so React knows it's safe to skip a re-render. However, for this to work, the node has to *actually be the same object*, not merely look the same in code. This is what `useMemo` does in this example. -Manually wrapping JSX nodes into `useMemo` is not convenient. For example, you can't do this conditionally. This is usually you would wrap components with [`memo`](/reference/react/memo) instead of wrapping JSX nodes. +Manually wrapping JSX nodes into `useMemo` is not convenient. For example, you can't do this conditionally. This is usually why you would wrap components with [`memo`](/reference/react/memo) instead of wrapping JSX nodes.