diff --git a/09-styling.md b/09-styling.md index dccb24a3..ae844664 100644 --- a/09-styling.md +++ b/09-styling.md @@ -63,7 +63,7 @@ Using our example, the class name of `.header` isn't very specific. Not only cou > There is nothing magical about CSS modules other than it forces our build-tool to define custom CSS class names for us so we can work with less unique names. > We'll look into using CSS modules a bit later in our workflow. -React provides a no-so-new method for avoiding this problem entirely by allowing us to define styles inline along with our JSX. +React provides a not-so-new method for avoiding this problem entirely by allowing us to define styles inline along with our JSX. ## Inline styles diff --git a/13-repeating-elements.md b/13-repeating-elements.md index 4238bcbc..220ccf4e 100644 --- a/13-repeating-elements.md +++ b/13-repeating-elements.md @@ -87,7 +87,7 @@ Starting the app again with the command generated by the `create-react-app` comm However, if we open the developer console, we'll see we have an error printed out. This error is caused by the fact that React doesn't know how to keep track of the individual components in our list as each one just looks like a `
  • ` component. -For performance reasons, React uses the virtual DOM to attempt limit the number of DOM elements that need to be updated when it rerenders the view. That is if nothing has changed, React won't make the browser update anything to save on work. +For performance reasons, React uses the virtual DOM to attempt to limit the number of DOM elements that need to be updated when it rerenders the view. That is if nothing has changed, React won't make the browser update anything to save on work. This feature is really fantastic for building web applications, but sometimes we have to help React out by providing unique identifiers for nodes. Mapping over a list and rendering components in the map is one of those times. diff --git a/15-promises.md b/15-promises.md index 36403122..5083e122 100644 --- a/15-promises.md +++ b/15-promises.md @@ -168,7 +168,7 @@ A promise only ever has one of three states at any given time: * fulfilled (resolved) * rejected (error) -A _pending_ promise can only every lead to either a fulfilled state or a rejected state _once and only once_, which can avoid some pretty complex error scenarios. This means that we can only ever return a promise once. If we want to rerun a function that uses promises, we need to create a _new_ one. +A _pending_ promise can only ever lead to either a fulfilled state or a rejected state _once and only once_, which can avoid some pretty complex error scenarios. This means that we can only ever return a promise once. If we want to rerun a function that uses promises, we need to create a _new_ one. ## Creating a promise diff --git a/19-intro-to-redux.md b/19-intro-to-redux.md index e7d930f5..5881c237 100644 --- a/19-intro-to-redux.md +++ b/19-intro-to-redux.md @@ -11,7 +11,7 @@ introBannerUrl: '/assets/images/series/30-days-of-react/headings/19_wide.jpg' date: Wed Oct 22 2016 21:29:42 GMT-0700 (PDT) --- -Yesterday, we discussed (in light detail) the reason for the Flux pattern, what is is, the different options we have available to us, as well as introduced [Redux](http://redux.js.org/). +Yesterday, we discussed (in light detail) the reason for the Flux pattern, what it is, the different options we have available to us, as well as introduced [Redux](http://redux.js.org/). Today, we are going to get back to code and on to adding Redux in our app. The app we're building with it right now is bare-bones simple, which will just show us the last time the page fetched the current time. For simplicity for now, we won't call out to a remote server, just using the JavaScript `Date` object. @@ -171,7 +171,7 @@ The error redux is giving us is telling us that we don't have a reducer inside o ## Reducers -The term `reducer` is just a fancy way of saying functions that return state. When we talk about a reducer, we are talking about this single function that gets executed when an action is fired. It can either handle the action (i.e. create a new state for it's piece of the state tree) or not handle it and return the original state. +The term `reducer` is just a fancy way of saying functions that return state. When we talk about a reducer, we are talking about this single function that gets executed when an action is fired. It can either handle the action (i.e. create a new state for its piece of the state tree) or not handle it and return the original state. The reducer function receives two arguments when it's called: