minor spelling change on the "controlled input null value" cookbook entry
Connor McSheffrey committed
Oct 1, 2013 at 23:29 UTC
a4d7f3f907cf95dc93f2b216ae8ed195570fe0b9
2 files changed
+2
-2
docs/cookbook/cb-08-controlled-input-null-value tip.md
+1
-1
@@ -7,7 +7,7 @@ permalink: controlled-input-null-value-tip.html
7
8
With a controlled input component, specifying a `value` prevents the user from changing the input unless you desire so (more info [here](forms.html)).
9
10
-You might have ran into a problem where you specified a `value` but the input can still be changed. In this case, you might have accidentally set your `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text be edited.
10
+You might have ran into a problem where you specified a `value` but the input can still be changed. In this case, you might have accidentally set your `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text can be edited.
11
12
```js
13
/** @jsx React.DOM */
docs/cookbook/cb-08-controlled-input-null-value.md
+1
-1
@@ -9,7 +9,7 @@ permalink: controlled-input-null-value.html
9
You specified a `value` parameter for your form input, but the input value can still be modified, contrary to [what you'd expect](forms.html).
10
11
### Solution
12
-You might have accidentally set your `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text be edited.
12
+You might have accidentally set your `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text can be edited.
13
14
```js
15
/** @jsx React.DOM */