From f3a94876194b1876a67e0e87cd1368fe1977ad52 Mon Sep 17 00:00:00 2001
From: James Seppi <james.seppi@gmail.com>
Date: Thu, 17 Jul 2014 16:23:07 -0500
Subject: [PATCH] fix typo

Closes #1859.
---
 _posts/2014-07-13-react-v0.11-rc1.md | 2 +-
 _posts/2014-07-17-react-v0.11.md     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/_posts/2014-07-13-react-v0.11-rc1.md b/_posts/2014-07-13-react-v0.11-rc1.md
index 9f300a9f..17417196 100644
--- a/_posts/2014-07-13-react-v0.11-rc1.md
+++ b/_posts/2014-07-13-react-v0.11-rc1.md
@@ -29,7 +29,7 @@ Starting in React 0.11, `getDefaultProps()` is called only once when `React.crea
 
 ## Rendering to `null`
 
-Since React's release, people have been using work arounds to "render nothing". Usually this means returning an empty `<div/>` or `<span/>`. Some people even got clever and started returning `<noscript/>` to avoid extraneous DOM nodes. We finally provided a "blessed" solution that allows developers to writing meaningful code. Returning `null` in an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `<noscript>` element, though in the future we hope to not put anything in the document. In the mean time, `<noscript>` elements do not affect layout in any way, so you can feel safe using `null` today!
+Since React's release, people have been using work arounds to "render nothing". Usually this means returning an empty `<div/>` or `<span/>`. Some people even got clever and started returning `<noscript/>` to avoid extraneous DOM nodes. We finally provided a "blessed" solution that allows developers to write meaningful code. Returning `null` is an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `<noscript>` element, though in the future we hope to not put anything in the document. In the mean time, `<noscript>` elements do not affect layout in any way, so you can feel safe using `null` today!
 
 ```js
 // Before
diff --git a/_posts/2014-07-17-react-v0.11.md b/_posts/2014-07-17-react-v0.11.md
index 802cbd07..93909208 100644
--- a/_posts/2014-07-17-react-v0.11.md
+++ b/_posts/2014-07-17-react-v0.11.md
@@ -32,7 +32,7 @@ Starting in React 0.11, `getDefaultProps()` is called only once when `React.crea
 
 ## Rendering to `null`
 
-Since React's release, people have been using work arounds to "render nothing". Usually this means returning an empty `<div/>` or `<span/>`. Some people even got clever and started returning `<noscript/>` to avoid extraneous DOM nodes. We finally provided a "blessed" solution that allows developers to writing meaningful code. Returning `null` in an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `<noscript>` element, though in the future we hope to not put anything in the document. In the mean time, `<noscript>` elements do not affect layout in any way, so you can feel safe using `null` today!
+Since React's release, people have been using work arounds to "render nothing". Usually this means returning an empty `<div/>` or `<span/>`. Some people even got clever and started returning `<noscript/>` to avoid extraneous DOM nodes. We finally provided a "blessed" solution that allows developers to write meaningful code. Returning `null` is an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `<noscript>` element, though in the future we hope to not put anything in the document. In the mean time, `<noscript>` elements do not affect layout in any way, so you can feel safe using `null` today!
 
 ```js
 // Before