Merge pull request #733 from rouzbeh84/lower-case

Lower Casing webpack

Author: bebraw

README.md

@@ -2,7 +2,7 @@
 
 # webpack.js.org
 
-Guides, documentation, and all things Webpack.
+Guides, documentation, and all things webpack.
 
 ## Contributing
 

antwar.config.js

@@ -148,7 +148,7 @@ module.exports = {
         return combineContexts(content, generated);
       }
     ),
-    
+
     vote: {
       path() {
         return require('./components/vote/list.jsx').default
@@ -177,7 +177,7 @@ module.exports = {
 
 function root(contentCb) {
   return {
-    title: 'Webpack',
+    title: 'webpack',
     path: function() { // Load path content
       return contentCb();
     },

components/organization/projects.json

@@ -15,7 +15,7 @@
 	{
 		"repo": "webpack/loader-utils",
 		"npm": "loader-utils",
-		"description": "Webpack loader utilities.",
+		"description": "webpack loader utilities.",
 		"maintainer": "sokra"
 	},
 	{
@@ -289,4 +289,3 @@
 		"maintainer": "thelarkinn"
 	}
 ]
-	

components/site/site.jsx

@@ -28,8 +28,8 @@ export default props => {
       }))
     }));
 
-  // Rename the root section ("Webpack" => "Other") and push it to the end
-  let rootIndex = sections.findIndex(section => section.title === 'Webpack');
+  // Rename the root section ("webpack" => "Other") and push it to the end
+  let rootIndex = sections.findIndex(section => section.title === 'webpack');
   let rootSection = sections.splice(rootIndex, 1)[0];
   rootSection.title = 'Other';
   sections.push(rootSection);

content/concepts/output.md

@@ -7,7 +7,7 @@ contributors:
   - rouzbeh84
 ---
 
-Options affecting the output of the compilation. `output` options tell Webpack how to write the compiled files to disk. Note, that while there can be multiple `entry` points, only one `output` configuration is specified.
+Options affecting the output of the compilation. `output` options tell webpack how to write the compiled files to disk. Note, that while there can be multiple `entry` points, only one `output` configuration is specified.
 
 If you use any hashing (`[hash]` or `[chunkhash]`), make sure to have a consistent ordering of modules. Use the `OccurrenceOrderPlugin` or `recordsPath`.
 

content/configuration/entry-context.md

@@ -7,7 +7,7 @@ contributors:
   - tarang9211
 ---
 
-The entry object is where Webpack looks to start building the bundle. The context is an absolute string to the directory that contains the entry files.
+The entry object is where webpacklooks to start building the bundle. The context is an absolute string to the directory that contains the entry files.
 
 ## `context`
 

content/configuration/index.md

@@ -10,7 +10,7 @@ contributors:
   - terinjokes
 ---
 
-Webpack is fed via a configuration object. It is passed in one of two ways depending on how you are using webpack: through the terminal or via Node.js. All the available configuration options are specified below.
+webpack is fed via a configuration object. It is passed in one of two ways depending on how you are using webpack: through the terminal or via Node.js. All the available configuration options are specified below.
 
 T> New to webpack? Check out our guide to some of webpack's [core concepts](/concepts) to get started!
 
@@ -148,7 +148,7 @@ var path = require('path');
 
         [loader](/configuration/module#rule-loader): "babel-loader",
         // the loader which should be applied, it'll be resolved relative to the context
-        // -loader suffix is no longer optional in Webpack 2 for clarity reasons
+        // -loader suffix is no longer optional in webpack2 for clarity reasons
         // see [webpack 1 upgrade guide](/guides/migrating)
 
         [options](/configuration/module#rule-options-rule-query): {

content/configuration/watch.md

@@ -7,7 +7,7 @@ contributors:
   - SpaceK33z
 ---
 
-Webpack can watch files and recompile whenever they change. This page explains how to enable this and a couple of tweaks you can make if watching does not properly for you.
+webpack can watch files and recompile whenever they change. This page explains how to enable this and a couple of tweaks you can make if watching does not properly for you.
 
 ## `watch`
 

content/development/how-to-write-a-plugin.md

@@ -3,24 +3,24 @@ title: How to write a plugin?
 sort: 2
 ---
 
-Plugins expose the full potential of the Webpack engine to third-party developers. Using staged build callbacks, developers can introduce their own behaviors into the Webpack build process. Building plugins is a bit more advanced than building loaders, because you'll need to understand some of the Webpack low-level internals to hook into them. Be prepared to read some source code!
+Plugins expose the full potential of the webpack engine to third-party developers. Using staged build callbacks, developers can introduce their own behaviors into the webpack build process. Building plugins is a bit more advanced than building loaders, because you'll need to understand some of the webpack low-level internals to hook into them. Be prepared to read some source code!
 
 ## Compiler and Compilation
 
-Among the two most important resources while developing plugins are the `compiler` and `compilation` objects. Understanding their roles is an important first step in extending the Webpack engine.
+Among the two most important resources while developing plugins are the `compiler` and `compilation` objects. Understanding their roles is an important first step in extending the webpack engine.
 
-- The `compiler` object represents the fully configured Webpack environment. This object is built once upon starting Webpack, and is configured with all operational settings including options, loaders, and plugins. When applying a plugin to the Webpack environment, the plugin will receive a reference to this compiler. Use the compiler to access the main Webpack environment.
+- The `compiler` object represents the fully configured webpack environment. This object is built once upon starting webpack, and is configured with all operational settings including options, loaders, and plugins. When applying a plugin to the webpack environment, the plugin will receive a reference to this compiler. Use the compiler to access the main webpack environment.
 
-- A `compilation` object represents a single build of versioned assets. While running Webpack development middleware, a new compilation will be created each time a file change is detected, thus generating a new set of compiled assets. A compilation surfaces information about the present state of module resources, compiled assets, changed files, and watched dependencies. The compilation also provides many callback points at which a plugin may choose to perform custom actions.
+- A `compilation` object represents a single build of versioned assets. While running webpack development middleware, a new compilation will be created each time a file change is detected, thus generating a new set of compiled assets. A compilation surfaces information about the present state of module resources, compiled assets, changed files, and watched dependencies. The compilation also provides many callback points at which a plugin may choose to perform custom actions.
 
-These two components are an integral part of any Webpack plugin (especially a `compilation`), so developers will benefit by familiarizing themselves with these source files:
+These two components are an integral part of any webpack plugin (especially a `compilation`), so developers will benefit by familiarizing themselves with these source files:
 
 - [Compiler Source](https://github.com/webpack/webpack/blob/master/lib/Compiler.js)
 - [Compilation Source](https://github.com/webpack/webpack/blob/master/lib/Compilation.js)
 
 ## Basic plugin architecture
 
-Plugins are instanceable objects with an `apply` method on their prototype. This `apply` method is called once by the Webpack compiler while installing the plugin. The `apply` method is given a reference to the underlying Webpack compiler, which grants access to compiler callbacks. A simple plugin is structured as follows:
+Plugins are instanceable objects with an `apply` method on their prototype. This `apply` method is called once by the webpack compiler while installing the plugin. The `apply` method is given a reference to the underlying webpack compiler, which grants access to compiler callbacks. A simple plugin is structured as follows:
 
 ```javascript
 function HelloWorldPlugin(options) {
@@ -36,7 +36,7 @@ HelloWorldPlugin.prototype.apply = function(compiler) {
 module.exports = HelloWorldPlugin;
 ```
 
-Then to install the plugin, just include an instance in your Webpack config `plugins` array:
+Then to install the plugin, just include an instance in your webpack config `plugins` array:
 
 ```javascript
 var HelloWorldPlugin = require('hello-world');
@@ -115,7 +115,7 @@ FileListPlugin.prototype.apply = function(compiler) {
       filelist += ('- '+ filename +'\n');
     }
 
-    // Insert this list into the Webpack build as a new file asset:
+    // Insert this list into the webpack build as a new file asset:
     compilation.assets['filelist.md'] = {
       source: function() {
         return filelist;

content/development/plugin-patterns.md

@@ -51,7 +51,7 @@ module.exports = MyPlugin;
 
 ### Monitoring the watch graph
 
-While running Webpack middleware, each compilation includes a `fileDependencies` array (what files are being watched) and a `fileTimestamps` hash that maps watched file paths to a timestamp. These are extremely useful for detecting what files have changed within the compilation:
+While running webpack middleware, each compilation includes a `fileDependencies` array (what files are being watched) and a `fileTimestamps` hash that maps watched file paths to a timestamp. These are extremely useful for detecting what files have changed within the compilation:
 
 ```javascript
 function MyPlugin() {