Merge pull request #904 from tobycheese/typos_wording

Typos and improved wording

1-js/11-async/01-callbacks/article.md

@@ -262,7 +262,7 @@ function step3(error, script) {
 
 See? It does the same, and there's no deep nesting now because we made every action a separate top-level function.
 
-It works, but the code looks like a torn apart spreadsheet. It's difficult to read, and you probably noticed that. One needs to eye-jump between pieces while reading it. That's inconvenient, especially if the reader is not familiar with the code and doesn't know where to eye-jump.
+It works, but the code looks like a torn apart spreadsheet. It's difficult to read, and you probably noticed that one needs to eye-jump between pieces while reading it. That's inconvenient, especially if the reader is not familiar with the code and doesn't know where to eye-jump.
 
 Also, the functions named `step*` are all of single use, they are created only to avoid the "pyramid of doom." No one is going to reuse them outside of the action chain. So there's a bit of a namespace cluttering here.
 

5-network/01-fetch-basics/article.md

@@ -3,7 +3,7 @@
 
 Method `fetch()` is the modern way of sending requests over HTTP.
 
-Is evolved for several years and continues to improve, right now the support is pretty solid among browsers.
+It evolved for several years and continues to improve, right now the support is pretty solid among browsers.
 
 The basic syntax is:
 

7-animation/3-js-animation/article.md

@@ -8,7 +8,7 @@ For instance, moving along a complex path, with a timing function different from
 
 An animation can be implemented as a sequence of frames -- usually small changes to HTML/CSS properties.
 
-For instance, changing `style.left` from `0px` to `100px` moves the element. And if we increase it in `setInterval`, changing by `2px` with a tiny delay, like 50 times per second, then it looks smooth. That's the same principle as in the cinema: 24 or more frames per second is enough to make it look smooth.
+For instance, changing `style.left` from `0px` to `100px` moves the element. And if we increase it in `setInterval`, changing by `2px` with a tiny delay, like 50 times per second, then it looks smooth. That's the same principle as in the cinema: 24 frames per second is enough to make it look smooth.
 
 The pseudo-code can look like this: