CommonJs -> CommonJS

Author: tkrotoff

content/concepts/configuration.md

@@ -7,7 +7,7 @@ contributors:
 
 You may have noticed that few webpack configurations look exactly alike. This is because **webpack's configuration file is a JavaScript file that exports an object.** This object is then processed by webpack based upon its defined properties.
 
-Because it's a standard node.js CommonJs module, you **can do the following**:
+Because it's a standard node.js CommonJS module, you **can do the following**:
 
 * import other files via `require(...)`
 * use utilities on npm via `require(...)`

content/configuration/index.md

@@ -52,7 +52,7 @@ T> Notice that throughout the configuration we use Node's built-in [path module]
 
     <details><summary>[libraryTarget](/configuration/output#output-librarytarget): "umd", // enum</summary>
     [libraryTarget](/configuration/output#output-librarytarget): "umd-module", // ES2015 module wrapped in UMD
-    [libraryTarget](/configuration/output#output-librarytarget): "commonjs-module", // ES2015 module wrapped in CommonJs
+    [libraryTarget](/configuration/output#output-librarytarget): "commonjs-module", // ES2015 module wrapped in CommonJS
     [libraryTarget](/configuration/output#output-librarytarget): "commonjs2", // exported with module.exports
     [libraryTarget](/configuration/output#output-librarytarget): "commonjs", // exported as properties to exports
     [libraryTarget](/configuration/output#output-librarytarget): "amd", // defined with AMD defined method

content/configuration/module.md

@@ -137,7 +137,7 @@ For each different parser options object a new parser is created and plugins can
 ``` js-with-links
 parser: {
   amd: false, // disable AMD
-  commonjs: false, // disable CommonJs
+  commonjs: false, // disable CommonJS
   system: false, // disable System
   harmony: false, // disable harmony import/export
   requireInclude: false, // disable require.include

content/configuration/target.md

@@ -20,7 +20,7 @@ Tells webpack which environment the application is targeting. The following valu
 | `target`      | Description            |
 | ------------- |------------------------|
 | `async-node`| Compile for usage in a Node.js-like environment (uses `fs` and `vm` to load chunks asynchronously)    |
-| `electron`      | Compile for [Electron](http://electron.atom.io/) renderer process, provide a target using `JsonpTemplatePlugin`, `FunctionModulePlugin` for browser environments and `NodeTargetPlugin` and `ExternalsPlugin` for CommonJs and Electron built-in modules. |
+| `electron`      | Compile for [Electron](http://electron.atom.io/) renderer process, provide a target using `JsonpTemplatePlugin`, `FunctionModulePlugin` for browser environments and `NodeTargetPlugin` and `ExternalsPlugin` for CommonJS and Electron built-in modules. |
 | `electron-renderer` | Compile for [Electron](http://electron.atom.io/) for `renderer-process` |
 | `node` | Compile for usage in a Node.js-like environment (uses Node.js `require` to load chunks) |
 |`node-webkit`|  Compile for usage in WebKit and uses JSONP for chunk loading. Allows importing of built-in Node.js modules and [`nw.gui`](http://docs.nwjs.io/en/latest/) (experimental) |

content/get-started/why-webpack.md

@@ -33,9 +33,9 @@ webpack however is not the only module bundler out there. If you are choosing be
 | AMD `define` | **yes** | **yes** | [deamdify](https://github.com/jaredhanson/deamdify) | yes | no | yes |
 | AMD `require` | **yes** | **yes** | no | yes | no | yes |
 | AMD `require` loads on demand | **yes** | with manual configuration | no | yes | no | no |
-| CommonJs `exports` | **yes** | only wrapping in `define` | **yes** | yes | [commonjs-plugin](https://github.com/rollup/rollup-plugin-commonjs) | yes |
-| CommonJs `require` | **yes** | only wrapping in `define` | **yes** | yes | [commonjs-plugin](https://github.com/rollup/rollup-plugin-commonjs) | yes |
-| CommonJs `require.resolve` | **yes** | no | no | no | no |
+| CommonJS `exports` | **yes** | only wrapping in `define` | **yes** | yes | [commonjs-plugin](https://github.com/rollup/rollup-plugin-commonjs) | yes |
+| CommonJS `require` | **yes** | only wrapping in `define` | **yes** | yes | [commonjs-plugin](https://github.com/rollup/rollup-plugin-commonjs) | yes |
+| CommonJS `require.resolve` | **yes** | no | no | no | no |
 | Concat in require `require("./fi" + "le")` | **yes** | no♦ | no | no | no |
 | Debugging support | **SourceUrl, SourceMaps** | not required | SourceMaps | **SourceUrl, SourceMaps** | **SourceUrl, SourceMaps** | SourceMaps |
 | Dependencies | 19MB / 127 packages | 11MB / 118 packages | **1.2MB / 1 package** | 26MB / 131 packages | ?MB / 3 packages

content/guides/author-libraries.md

@@ -27,7 +27,6 @@ export function wordToNum(word) {
         return ref.word === word && word.toLowerCase() ? ref.num : accum;
     }, -1);
 };
-
 ```
 
 The usage spec for the library will be as follows.
@@ -41,7 +40,7 @@ import * as webpackNumbers from 'webpack-numbers';
 webpackNumbers.wordToNum('Two') // output is 2
 ...
 
-// CommonJs modules
+// CommonJS modules
 
 var webpackNumbers = require('webpack-numbers');
 
@@ -140,7 +139,7 @@ This means that your library expects a dependency named `lodash` to be available
 
 ### Add `libraryTarget`
 
-For widespread use of the library, we would like it to be compatible in different environments, i. e. CommonJs, AMD, Node.js and as a global variable.
+For widespread use of the library, we would like it to be compatible in different environments, i. e. CommonJS, AMD, Node.js and as a global variable.
 
 To make your library available for reuse, add `library` property in webpack configuration.
 

content/guides/shimming.md

@@ -8,7 +8,7 @@ contributors:
 
 `webpack` as a module bundler can understand modules written as ES2015 modules, CommonJS or AMD. But many times, while using third party libraries, we see that they expect dependencies which are global aka `$` for `jquery`. They might also be creating global variables which need to be exported. Here we will see different ways to help webpack understand these __broken modules__.
 
-## Prefer unminified CommonJs/AMD files over bundled `dist` versions.
+## Prefer unminified CommonJS/AMD files over bundled `dist` versions.
 
 Most modules link the `dist` version in the `main` field of their `package.json`. While this is useful for most developers, for webpack it is better to alias the src version because this way webpack is able to optimize dependencies better (e.g. when using the [DedupePlugin](/concepts/plugins#DedupePlugin)). However in most cases `dist` works fine as well.