From 5a084dd028d6eab9023f3909e6ec90c73b75f591 Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Sat, 7 Oct 2017 08:06:06 -0700 Subject: [PATCH] Wording nits --- content/docs/forms.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/docs/forms.md b/content/docs/forms.md index 5a84d915..8136e42d 100644 --- a/content/docs/forms.md +++ b/content/docs/forms.md @@ -266,11 +266,9 @@ Also, since `setState()` automatically [merges a partial state into the current ## Controlled Input Null Value -Specifying the value prop on a [controlled component](/docs/forms.html#controlled-components) prevents the user from changing the input unless you desire so. +Specifying the value prop on a [controlled component](/docs/forms.html#controlled-components) prevents the user from changing the input unless you desire so. If you've specified a `value` but the input is still editable, you may have accidentally set `value` to `undefined` or `null`. -You might have encountered a situation where value is specified but an input is still editable. In this case you might have accidentally set value to undefined or null. - -The following code demonstrates this. (The input becomes editable after a short delay.) +The following code demonstrates this. (The input is locked at first but becomes editable after a short delay.) ```javascript ReactDOM.render(, mountNode);