Merge pull request reactjs#38 from lizell/master

 Added IntelliJ project files ignore and fixed minor spelings

Author: happypoulp

.gitignore

@@ -3,4 +3,5 @@ npm-debug.log
 .DS_Store
 dist
 nested-dispatch.js
-test.js
+test.js
+.idea

05_get-state.js

@@ -102,7 +102,7 @@ console.log('redux state after initialization:', store_3.getState())
 //        - using Object.assign (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign)
 //        - using manual merge
 //        - or whatever other strategy that suits your needs and the structure of your state since
-//          Redux is absolutely NOT opiniated on this (remember, Redux is a state container).
+//          Redux is absolutely NOT opinionated on this (remember, Redux is a state container).
 
 // Now that we're starting to handle actions in our reducer let's speak about having multiple reducers and
 // combining them.

08_dispatch-async-action-1.js

@@ -7,7 +7,7 @@
 // that produce an action synchronously: when called, an action is returned immediately.
 
 // Let's now imagine a simple asynchronous use-case:
-// 1) user clicks on button "Say Hi in 2 second"
+// 1) user clicks on button "Say Hi in 2 seconds"
 // 2) When button "A" is clicked, we'd like to show message "Hi" after 2 seconds have elapsed
 // 3) 2 seconds later, our view is updated with the message "Hi"
 

09_dispatch-async-action-2.js

@@ -44,7 +44,7 @@ store_0.dispatch(asyncSayActionCreator_1('Hi'))
 //     ...
 
 // It seems that our function didn't even reach our reducers. But Redux has been kind enough to give us a
-// tips: "Use custom middleware for async actions.". It looks like we're on the right path but what is this 
+// tip: "Use custom middleware for async actions.". It looks like we're on the right path but what is this
 // "middleware" thing?
 
 // Just to reassure you, our action creator asyncSayActionCreator_1 is well-written and will work as expected

11_state-subscriber.js

@@ -62,7 +62,7 @@ store_0.dispatch(addItemActionCreator({ id: 1234, description: 'anything' }))
 
 // Our subscribe callback is correctly called and our store now contains the new item that we added.
 
-// Theorically speaking we could stop here. Our Flux loop is closed, we understood all concepts that make
+// Theoretically speaking we could stop here. Our Flux loop is closed, we understood all concepts that make
 // Flux and we saw that it is not that much of a mystery. But to be honest, there is still a lot to talk
 // about and a few things in the last example were intentionally left aside to keep the simplest form of this
 // last Flux's concept:

12_src/src/create-store.js

@@ -6,13 +6,13 @@
 // One thing to notice though: we're not using the thunk middleware that we've seen before. Instead
 // we use a promise middleware solution that will allow us to handle asynchronous action creators and
 // to do some nice real time updates on our UI (could also be some optimistic updates).
-// This middleware was discussed here:  https://github.com/gaearon/redux/issues/99 and it is used
+// This middleware was discussed here: https://github.com/gaearon/redux/issues/99 and it is used
 // in this very good react-redux-universal-example: https://github.com/erikras/react-redux-universal-hot-example
 // that I strongly suggest you get a look at (later, not right now ;)).
 
 import { createStore, applyMiddleware, combineReducers } from 'redux'
-// You can go and see code for this middleware, it's not very complicated and makes a good
-// excercise to sharpen your understanding on middlewares.
+// You can go and see the code for this middleware, it's not very complicated and makes a good
+// exercise to sharpen your understanding on middlewares.
 import promiseMiddleware from './promise-middleware'
 // We'll just have one reducer in this application but the ES6 import notation below is
 // pretty interesting to import and produce a reducers hash in one go. Have a look in

12_src/src/home.jsx

@@ -21,7 +21,7 @@
 import React from 'react'
 import { connect } from 'react-redux'
 // We use the same ES6 import trick to get all action creators and produce a hash like we did with
-// our reducers. If you haven't yet, go get a look at our action creator (./actions-creator.js).
+// our reducers. If you haven't yet, go get a look at our action creator (./actions-creators.js).
 import * as actionCreators from './action-creators'
 
 // The "connect" decorator takes as its only parameter, a function that will select which slice of your
@@ -74,4 +74,4 @@ export default class Home extends React.Component {
   }
 }
 
-// Go to ./final-words.jsx for our last advice about what to do now...
+// Go to ./13_final-words.js for our last advice about what to do now...