Merge pull request #183 from thefourtheye/fix-minor-grammatical-mistakes

fix minor grammatical mistakes

locale/en/docs/es6.md

@@ -4,11 +4,11 @@ layout: docs.hbs
 ---
 # ES6 in Node.js
 
-Node.js is built against modern versions of [V8](https://developers.google.com/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to Node.js developers in a timely manner, as well as continued performance and stability improvements.
+Node.js is built against modern versions of [V8](https://developers.google.com/v8/). By keeping up-to-date with the latest releases of this engine, we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to Node.js developers in a timely manner, as well as continued performance and stability improvements.
 
-All ES6 features are split into three groups for **shipping**, **staged** and **in progress** features:
+All ES6 features are split into three groups for **shipping**, **staged**, and **in progress** features:
 
-* All **shipping** features, which V8 considers stable are turned **on by default on Node.js** and do **NOT** require any kind of runtime flag.
+* All **shipping** features, which V8 considers stable, are turned **on by default on Node.js** and do **NOT** require any kind of runtime flag.
 * **Staged** features, which are almost-completed features that are not considered stable by the V8 team, require a runtime flag: `--es_staging` (or its synonym, `--harmony`).
 * **In progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_destructuring`), although this is highly discouraged unless for testing purposes.
 

locale/en/docs/index.md

@@ -5,9 +5,9 @@ layout: docs.hbs
 
 # About Docs
 
-It's important for Node.js to provide documentation to its users, but documentation means different things to different people. Here on nodejs.org you will find three types of documentation, reference documentation, ES6 features and frequently asked questions.
+It's important for Node.js to provide documentation to its users, but documentation means different things to different people. Here, on nodejs.org, you will find three types of documentation, reference documentation, ES6 features, and frequently asked questions.
 
-Our [API reference documentation](/api/) is meant to provide detailed version information about a given method or pattern in Node.js. From this documentation you should be able to identify what input a method has, the return value of that method, and what if any errors may be related to method. You should also be able to identify which methods are available for different versions of Node.js.
+Our [API reference documentation](/api/) is meant to provide detailed version information about a given method or pattern in Node.js. From this documentation you should be able to identify what input a method has, the return value of that method, and what, if any, errors may be related to that method. You should also be able to identify which methods are available for different versions of Node.js.
 
 <div class="highlight-box">
     <h3>Looking for API docs of previous releases?</h3>
@@ -19,8 +19,9 @@ Our [API reference documentation](/api/) is meant to provide detailed version in
     </ul>
 </div>
 
-The [ES6 section](/en/docs/es6/) describes the three different features groups and which ones are enabled by default in Node.js. It lists out all the different features enabled by default alongside explanatory links. Also, it shows how to find the exact version of V8 a Node.js release has.
+The [ES6 section](/en/docs/es6/) describes the three different features groups and which ones are enabled by default in Node.js. It lists out all the different features enabled by default, alongside explanatory links. Also, it shows how to find the exact version of V8 a Node.js release has.
 
-Our [FAQ](/en/docs/faq/) shows how everyone can contribute to Node.js, our code of conduct and governance model. How to get in touch on github and IRC and helping out triaging issues.
+Our [FAQ](/en/docs/faq/) shows how everyone can contribute to Node.js, our code of conduct,
+governance model, how to get in touch on github and IRC, and helping out triaging issues.
 
-All of this documentation is meant to only highlight the builtin core modules provided by Node, and not to highlight the module and collection of modules found in the community. Node.js doesn't want to be in the business of picking winners or losers, so to avoid the appearance of favoritism we only discuss our APIs.
+This documentation is meant only to describe the builtin core modules provided by Node.js, not to highlight any particular module or collection of modules found in the community.