diff --git a/cookbook/cb-08-controlled-input-null-value tip.md b/cookbook/cb-08-controlled-input-null-value tip.md
index acda5693..2febcaf7 100644
--- a/cookbook/cb-08-controlled-input-null-value tip.md	
+++ b/cookbook/cb-08-controlled-input-null-value tip.md	
@@ -7,7 +7,7 @@ permalink: controlled-input-null-value-tip.html
 
 With a controlled input component, specifying a `value` prevents the user from changing the input unless you desire so (more info [here](forms.html)).
 
-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.
+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.
 
 ```js
 /** @jsx React.DOM */
diff --git a/cookbook/cb-08-controlled-input-null-value.md b/cookbook/cb-08-controlled-input-null-value.md
index b2d002aa..0bcf11c4 100644
--- a/cookbook/cb-08-controlled-input-null-value.md
+++ b/cookbook/cb-08-controlled-input-null-value.md
@@ -9,7 +9,7 @@ permalink: controlled-input-null-value.html
 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).
 
 ### Solution
-You might have accidentally set your `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text be edited.
+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.
 
 ```js
 /** @jsx React.DOM */