From b0d1cbd1027ed25c22d830e42ef46b36349ec8a8 Mon Sep 17 00:00:00 2001 From: Kevin Barabash Date: Thu, 4 Jul 2024 17:52:08 -0400 Subject: [PATCH] fix typo --- src/react-render-perf/lesson-02/content.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/react-render-perf/lesson-02/content.mdx b/src/react-render-perf/lesson-02/content.mdx index ee7fa10..6cbf66f 100644 --- a/src/react-render-perf/lesson-02/content.mdx +++ b/src/react-render-perf/lesson-02/content.mdx @@ -151,7 +151,7 @@ const Bar = React.memo(() => { the long term I think we should evaluate possible replaces for redux that don't have this preformance issue like jotai, zustand, or recoil.js. - React.useMemo(callback) and React.memo(Component, arePropsEqual?) are - both use to memoize things. The former is used for memoizing computations _within_ a functional + both used to memoize things. The former is used for memoizing computations _within_ a functional component while the latter is used for memoizing functional components themselves. ## Exercise