From c47933a3143dfff20c0eb234e5b58584b5727681 Mon Sep 17 00:00:00 2001 From: Jonathan Berger Date: Fri, 22 Jun 2018 03:57:48 -0700 Subject: [PATCH] Correct typo in FAQ (#985) Correcting a small typo. --- content/docs/faq-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/faq-state.md b/content/docs/faq-state.md index ee8a8341..e92717f2 100644 --- a/content/docs/faq-state.md +++ b/content/docs/faq-state.md @@ -22,7 +22,7 @@ Here are some good resources for further reading on when to use `props` vs `stat In React, both `this.props` and `this.state` represent the *rendered* values, i.e. what's currently on the screen. -Calls to `setState` are asynchronous - don't rely on `this.state` to reflect the new value immediately after calling `setState`. Pass an updater function instead of an object if you need compute values based on the current state (see below for details). +Calls to `setState` are asynchronous - don't rely on `this.state` to reflect the new value immediately after calling `setState`. Pass an updater function instead of an object if you need to compute values based on the current state (see below for details). Example of code that will *not* behave as expected: