From a06d860f34eaccc6b618292bfe439621fb53220f Mon Sep 17 00:00:00 2001 From: Mayank <9084735+mayank99@users.noreply.github.com> Date: Sat, 12 Feb 2022 10:21:42 -0500 Subject: [PATCH] Fix broken link in render-and-commit.md (#4327) `/reference/setState` -> `/apis/usestate#setstate` --- beta/src/pages/learn/render-and-commit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/beta/src/pages/learn/render-and-commit.md b/beta/src/pages/learn/render-and-commit.md index 1f048c61..3b7ec18b 100644 --- a/beta/src/pages/learn/render-and-commit.md +++ b/beta/src/pages/learn/render-and-commit.md @@ -69,7 +69,7 @@ Try commenting out the `ReactDOM.render` call and see the component disappear! ### Re-renders when state updates {/*re-renders-when-state-updates*/} -Once the component has been initially rendered, you can trigger further renders by updating its state with [`setState`](reference/setstate). Updating your component's state automatically queues a render. (You can imagine these as a restaurant guest ordering tea, dessert, and all sorts of things after putting in their first order, depending on the state of their thirst or hunger.) +Once the component has been initially rendered, you can trigger further renders by updating its state with the [`set` function](/apis/usestate#setstate). Updating your component's state automatically queues a render. (You can imagine these as a restaurant guest ordering tea, dessert, and all sorts of things after putting in their first order, depending on the state of their thirst or hunger.)