Hopefully clarify [Concepts/Output](concepts/output.md) and [Concepts/Targets](concepts/targets.md) little bit further as well as some general spelling/grammar (please don't hate me) updates

Author: Rouzbeh Sarrafieh

content/concepts/configuration.md

@@ -158,7 +158,7 @@ In the example below JSX (React JavaScript Markup) and Babel are used to create
 ```javascript
 import h from 'jsxobj';
 
-// example of an import'd plugin
+// example of an imported plugin
 const CustomPlugin = config => ({
   ...config,
   name: 'custom-plugin'

content/concepts/hot-module-replacement.md

@@ -19,14 +19,14 @@ The app code asks the HMR runtime to check for updates. The HMR runtime download
 
 In addition to the normal assets the compiler need to emit the "Update" to allow updating from previous version to this version. The "Update" contains two parts:
 
-1. the update manifest (JSON)
-2. one or multiple update chunks (JavaScript)
+1. The update manifest (JSON)
+2. One or multiple update chunks (JavaScript)
 
 The manifest contains the new compilation hash and a list of all update chunks (2.).
 
 The update chunks contain code for all updated modules in this chunk (or a flag if a module was removed).
 
-The compiler addtionally makes sure that module and chunk ids are consistent between these builds. It uses a "records" json file to store them between builds (or it stores them in memory).
+The compiler additionally makes sure that module and chunk ids are consistent between these builds. It uses a "records" json file to store them between builds (or it stores them in memory).
 
 ### From The Module View
 
@@ -40,7 +40,7 @@ For the module system runtime additional code is emitted to track module `parent
 
 On the management side the runtime supports two methods: `check` and `apply`.
 
-A `check` does a HTTP request to the update manifest. When this request fails, there is no update available. Elsewise the list of updated chunks is compared to the list of currently loaded chunks. For each loaded chunk the corresponding update chunk is downloaded. All module updates as stored in the runtime as update. The runtime switches into the `ready` state, meaning an update has been downloaded and is ready to be applied.
+A `check` does a HTTP request to the update manifest. When this request fails, there is no update available. Otherwise, the list of updated chunks is compared to the list of currently loaded chunks. For each loaded chunk the corresponding update chunk is downloaded. All module updates as stored in the runtime as update. The runtime switches into the `ready` state, meaning an update has been downloaded and is ready to be applied.
 
 For each new chunk request in the ready state the update chunk is also downloaded.
 
@@ -52,6 +52,6 @@ Now all invalid modules are disposed (dispose handler) and unloaded. Then the cu
 
 You can use it in development as a LiveReload replacement. webpack-dev-server supports a hot mode which tries to update with HMR before trying to reload the whole page. See how to implement [HMR with React](/guides/hmr-react) for example.
 
-Some loaders already generate modules that are hot-updateable. i.e. the `style-loader` can exchange the stylesheet. You don't need to do anything special.
+Some loaders already generate modules that are hot-updatable. i.e. the `style-loader` can exchange the stylesheet. You don't need to do anything special.
 
-webpack's power lies in its customizability, and there are *many* ways of configuring HMR given the needs of a particular project.
+Webpack's power lies in its customizability, and there are *many* ways of configuring HMR given the needs of a particular project.

content/concepts/modules.md

@@ -39,6 +39,6 @@ The webpack community has built _loaders_ for a wide variety of popular language
 * [Less](http://lesscss.org)
 * [Stylus](http://stylus-lang.com)
 
-And many others! Overall, webpack provides a powerful and rich API for customization that allows one to use webpack for **any stack**, while staying **unopinionated** about your development, testing, and production workflows.
+And many others! Overall, webpack provides a powerful and rich API for customization that allows one to use webpack for **any stack**, while staying **non-opinionated** about your development, testing, and production workflows.
 
 For a full list, see [**the list of loaders**](https://webpack.github.io/docs/list-of-loaders.html) or [**write your own**](/api/loaders).

content/concepts/output.md

@@ -145,7 +145,7 @@ The filename of the Hot Update Main File. It is inside the `output.path` directo
 
 The JSONP function used by webpack for asnyc loading of chunks.
 
-A shorter function may reduce the filesize a bit. Use a different identifier when having multiple webpack instances on a single page.
+A shorter function may reduce the file size a bit. Use a different identifier when having multiple webpack instances on a single page.
 
 > Default: `"webpackJsonp"`
 

content/concepts/targets.md

@@ -21,9 +21,11 @@ module.exports = {
 };
 ```
 
+In the example above, using `node` webpack will compile for usage in a Node.js-like environment (uses Node.js `require` to load chunks and not touch any built in modules like `fs` or `path`).
+
 Each _target_ has a variety of deployment/environment specific additions, support to fit its needs. See what [targets are available](/configuration/target).
 
-?> We should expand on this further. What specifically is included.
+?>Further expansion for other popular target values
 
 ## Multiple Targets