diff --git a/_posts/2013-09-24-community-roundup-8.md b/_posts/2013-09-24-community-roundup-8.md
index b0df78b3..26102019 100644
--- a/_posts/2013-09-24-community-roundup-8.md
+++ b/_posts/2013-09-24-community-roundup-8.md
@@ -66,4 +66,4 @@ While this is not going to work for all the attributes since they are camelCased
[Vjeux](http://blog.vjeux.com/) re-implemented the display part of the IRC logger in React. Just 130 lines are needed for a performant infinite scroll with timestamps and color-coded author names.
-
+
diff --git a/_posts/2013-11-05-thinking-in-react.md b/_posts/2013-11-05-thinking-in-react.md
index 56125c2c..5688e892 100644
--- a/_posts/2013-11-05-thinking-in-react.md
+++ b/_posts/2013-11-05-thinking-in-react.md
@@ -56,7 +56,7 @@ Now that we've identified the components in our mock, let's arrange them into a
## Step 2: Build a static version in React
-
+
Now that you have your component hierarchy it's time to start implementing your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's easiest to decouple these processes because building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why.
@@ -100,7 +100,7 @@ So finally, our state is:
## Step 4: Identify where your state should live
-
+
OK, so we've identified what the minimal set of app state is. Next we need to identify which component mutates, or *owns*, this state.
@@ -125,7 +125,7 @@ You can start seeing how your application will behave: set `filterText` to `"bal
## Step 5: Add inverse data flow
-
+
So far we've built an app that renders correctly as a function of props and state flowing down the hierarchy. Now it's time to support data flowing the other way: the form components deep in the hierarchy need to update the state in `FilterableProductTable`.
diff --git a/_posts/2013-12-23-community-roundup-12.md b/_posts/2013-12-23-community-roundup-12.md
index 7def798c..820d8bf8 100644
--- a/_posts/2013-12-23-community-roundup-12.md
+++ b/_posts/2013-12-23-community-roundup-12.md
@@ -63,7 +63,7 @@ React declarative approach is well suited to write games. [Cheng Lou](https://gi
[Ross Allen](https://twitter.com/ssorallen) implemented [MontageJS](http://montagejs.org/)'s [Reddit tutorial](http://montagejs.org/docs/tutorial-reddit-client-with-montagejs.html) in React. This is a good opportunity to compare the philosophies of the two libraries.
-
+
[View the source on JSFiddle...](http://jsfiddle.net/ssorallen/fEsYt/)
diff --git a/_posts/2014-01-06-community-roundup-14.md b/_posts/2014-01-06-community-roundup-14.md
index a42c645c..7f5d61df 100644
--- a/_posts/2014-01-06-community-roundup-14.md
+++ b/_posts/2014-01-06-community-roundup-14.md
@@ -45,7 +45,7 @@ rails s
[Eldar Djafarov](http://eldar.djafarov.com/) implemented a mixin to link Backbone models to React state and a small abstraction to write two-way binding on-top.
-
+
[Check out the blog post...](http://eldar.djafarov.com/2013/11/reactjs-mixing-with-backbone/)
@@ -71,7 +71,7 @@ rails s
[Thomas Aylott](http://subtlegradient.com/) implemented an API that looks like Web Components but using React underneath.
-
+
## React vs Angular
diff --git a/docs/thinking-in-react.md b/docs/thinking-in-react.md
index 8885580d..f99ee0c4 100644
--- a/docs/thinking-in-react.md
+++ b/docs/thinking-in-react.md
@@ -11,10 +11,6 @@ React is, in my opinion, the premier way to build big, fast Web apps with JavaSc
One of the many great parts of React is how it makes you think about apps as you build them. In this post I'll walk you through the thought process of building a searchable product data table using React.
-> Note:
->
-> If you can't see the embedded code snippets on this page, make sure you're NOT loading this page on `https`.
-
## Start with a mock
Imagine that we already have a JSON API and a mock from our designer. Our designer apparently isn't very good because the mock looks like this:
@@ -64,7 +60,7 @@ Now that we've identified the components in our mock, let's arrange them into a
## Step 2: Build a static version in React
-
+
Now that you have your component hierarchy it's time to start implementing your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's easiest to decouple these processes because building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why.
@@ -108,7 +104,7 @@ So finally, our state is:
## Step 4: Identify where your state should live
-
+
OK, so we've identified what the minimal set of app state is. Next we need to identify which component mutates, or *owns*, this state.
@@ -133,7 +129,7 @@ You can start seeing how your application will behave: set `filterText` to `"bal
## Step 5: Add inverse data flow
-
+
So far we've built an app that renders correctly as a function of props and state flowing down the hierarchy. Now it's time to support data flowing the other way: the form components deep in the hierarchy need to update the state in `FilterableProductTable`.