From f0a9793dff9f8e86ec365bfadb0b4b23c6f618ce Mon Sep 17 00:00:00 2001 From: Siarhei Bobryk Date: Sun, 19 Sep 2021 13:14:11 +0300 Subject: [PATCH] [Docs] Apply the code Markdown syntax for the value prop (#3912) --- content/docs/forms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/forms.md b/content/docs/forms.md index 19ff42fe6..c43a72a3b 100644 --- a/content/docs/forms.md +++ b/content/docs/forms.md @@ -270,7 +270,7 @@ Also, since `setState()` automatically [merges a partial state into the current ## Controlled Input Null Value {#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. If you've specified a `value` but the input is still editable, you may have accidentally set `value` to `undefined` or `null`. +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`. The following code demonstrates this. (The input is locked at first but becomes editable after a short delay.)