From 335417aa97452b5aa41840c227b6d0c89b4c2689 Mon Sep 17 00:00:00 2001 From: DavidKessel <79220281+DavidKessel@users.noreply.github.com> Date: Thu, 24 Mar 2022 23:27:58 +0000 Subject: [PATCH] fix typo on page (#4490) Co-authored-by: David --- beta/src/pages/learn/sharing-state-between-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/beta/src/pages/learn/sharing-state-between-components.md b/beta/src/pages/learn/sharing-state-between-components.md index a068a6ea..1b0661f5 100644 --- a/beta/src/pages/learn/sharing-state-between-components.md +++ b/beta/src/pages/learn/sharing-state-between-components.md @@ -166,7 +166,7 @@ Lifting state up often changes the nature of what you're storing as state. The parent component passes the state setting function to both child components. -In this case, only one panel should be active at a time. This means that the `Accordion` common parent component needs to keep track of *which* panel is the active one. Instead of a `boolean` value, it could use an number as the index of the active `Panel` for the state variable: +In this case, only one panel should be active at a time. This means that the `Accordion` common parent component needs to keep track of *which* panel is the active one. Instead of a `boolean` value, it could use a number as the index of the active `Panel` for the state variable: ```js const [activeIndex, setActiveIndex] = useState(0);