diff --git a/examples/with-redux/README.md b/examples/with-redux/README.md
index 6b7d6759..71645417 100644
--- a/examples/with-redux/README.md
+++ b/examples/with-redux/README.md
@@ -28,7 +28,7 @@ now
Usually splitting your app state into `pages` feels natural but sometimes you'll want to have global state for your app. This is an example on how you can use redux that also works with our universal rendering approach. This is just a way you can do it but it's not the only one.
-In this example we are going to display a digital clock that updates every second. The first render is happening in the server and then the browser will take over. To illustrate this, the server rendered clock will have a different background color than the client one.
+In the first example we are going to display a digital clock that updates every second. The first render is happening in the server and then the browser will take over. To illustrate this, the server rendered clock will have a different background color than the client one.
![](http://i.imgur.com/JCxtWSj.gif)
@@ -43,3 +43,7 @@ To pass the initial state from the server to the client we pass it as a prop cal
The trick here for supporting universal redux is to separate the cases for the client and the server. When we are on the server we want to create a new store every time, otherwise different users data will be mixed up. If we are in the client we want to use always the same store. That's what we accomplish on `store.js`
The clock, under `components/Clock.js`, has access to the state using the `connect` function from `react-redux`. In this case Clock is a direct child from the page but it could be deep down the render tree.
+
+The second example, under `components/AddCount.js`, shows a simple add counter function with a class component implementing a common redux pattern of mapping state and props. Again, the first render is happening in the server and instead of starting the count at 0, it will dispatch an action in redux that starts the count at 1. This continues to highlight how each navigation triggers a server render first and then a client render second, when you navigate between pages.
+
+For simplicity and readability, Reducers, Actions, and Store creators are all in the same file: `store.js`
diff --git a/examples/with-redux/components/AddCount.js b/examples/with-redux/components/AddCount.js
new file mode 100644
index 00000000..2bf76f3a
--- /dev/null
+++ b/examples/with-redux/components/AddCount.js
@@ -0,0 +1,35 @@
+import React, {Component} from 'react'
+import { connect } from 'react-redux'
+import { bindActionCreators } from 'redux'
+import { addCount } from '../store'
+
+class AddCount extends Component {
+ add = () => {
+ this.props.addCount()
+ }
+
+ render () {
+ const { count } = this.props
+ return (
+