Merge pull request #693 from rouzbeh84/concepts-tweaking-ammend

formatting fixes and adding handle to contrib table

Author: bebraw

content/concepts/hot-module-replacement.md

@@ -5,6 +5,7 @@ contributors:
 - SpaceK33z
 - sokra
 - GRardB
+- rouzbeh84
 ---
 
 Hot Module Replacement (HMR) exchanges, adds, or removes

content/concepts/modules.md

@@ -4,6 +4,7 @@ sort: 7
 contributors:
   - TheLarkInn
   - simon04
+  - rouzbeh84
 ---
 
 In [modular programming](https://en.wikipedia.org/wiki/Modular_programming), developers break programs up into discrete chunks of functionality called a _module_.

content/concepts/output.md

@@ -4,13 +4,14 @@ sort: 3
 contributors:
   - TheLarkInn
   - chyipin
+  - 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.
 
 If you use any hashing (`[hash]` or `[chunkhash]`), make sure to have a consistent ordering of modules. Use the `OccurrenceOrderPlugin` or `recordsPath`.
 
-# Usage
+## Usage
 
 The minimum requirements for the `output` property in your webpack config is to set its value to an object including the following two things :
 
@@ -31,11 +32,11 @@ const config = {
 module.exports = config;
 ```
 
-# Options
+## Options
 
 The following is a list of values you can pass to the `output` property.
 
-## `output.chunkFilename`
+### `output.chunkFilename`
 
 The filename of non-entry chunks as a relative path inside the `output.path` directory.
 
@@ -47,7 +48,7 @@ The filename of non-entry chunks as a relative path inside the `output.path` dir
 
 `[chunkhash]` is replaced by the hash of the chunk.
 
-## `output.crossOriginLoading`
+### `output.crossOriginLoading`
 
 This option enables cross-origin loading of chunks.
 
@@ -63,9 +64,11 @@ For more information on cross-origin loading see [MDN](https://developer.mozilla
 
 > Default: `false`
 
-> see also [[library and externals]] see also [[Development Tools]]
+> see also [[library and externals]]
 
-## `output.devtoolLineToLine`
+> see also [[Development Tools]]
+
+### `output.devtoolLineToLine`
 
 Enable line-to-line mapped mode for all/specified modules. Line-to-line mapped mode uses a simple SourceMap where each line of the generated source is mapped to the same line of the original source. It's a performance optimization. Only use it if your performance needs to be better and you are sure that input lines match which generated lines.
 
@@ -75,7 +78,7 @@ An object `{test, include, exclude}` similar to `module.loaders` enables it for
 
 > Default: `false`
 
-## `output.filename`
+### `output.filename`
 
 Specifies the name of each output file on disk. You must **not** specify an absolute path here! The `output.path` option determines the location on disk the files are written. `filename` is used solely for naming the individual files.
 
@@ -118,7 +121,7 @@ If your configuration creates more than a single "chunk" (as with multiple entry
 // writes to disk: ./build/app.js, ./build/search.js
 ```
 
-## `output.hotUpdateChunkFilename`
+### `output.hotUpdateChunkFilename`
 
 The filename of the Hot Update Chunks. They are inside the `output.path` directory.
 
@@ -128,35 +131,35 @@ The filename of the Hot Update Chunks. They are inside the `output.path` directo
 
 > Default: `"[id].[hash].hot-update.js"`
 
-## `output.hotUpdateFunction`
+### `output.hotUpdateFunction`
 
 The JSONP function used by webpack for async loading of hot update chunks.
 
 > Default: `"webpackHotUpdate"`
 
-## `output.hotUpdateMainFilename`
+### `output.hotUpdateMainFilename`
 
 The filename of the Hot Update Main File. It is inside the `output.path` directory.
 
 `[hash]` is replaced by the hash of the compilation. (The last hash stored in the records)
 
 > Default: `"[hash].hot-update.json"`
 
-## `output.jsonpFunction`
+### `output.jsonpFunction`
 
 The JSONP function used by webpack for asnyc loading of chunks.
 
 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"`
 
-## `output.library`
+### `output.library`
 
 If set, export the bundle as library. `output.library` is the name.
 
 Use this if you are writing a library and want to publish it as single file.
 
-## `output.libraryTarget`
+### `output.libraryTarget`
 
 Which format to export the library:
 
@@ -176,7 +179,7 @@ Which format to export the library:
 
 If `output.library` is not set, but `output.libraryTarget` is set to a value other than `var`, every property of the exported object is copied (Except `amd`, `commonjs2` and `umd`).
 
-## `output.path`
+### `output.path`
 
 The output directory as an **absolute path** (required).
 
@@ -218,7 +221,7 @@ output: {
 // rest of your application entry
 ```
 
-## `output.sourceMapFilename`
+### `output.sourceMapFilename`
 
 The filename of the SourceMaps for the JavaScript files. They are inside the `output.path` directory.
 

content/concepts/plugins.md

@@ -4,6 +4,7 @@ sort: 5
 contributors:
   - TheLarkInn
   - jhnns
+  - rouzbeh84
 ---
 
 **Plugins** are the [backbone](https://github.com/webpack/tapable) of webpack. webpack itself is built on the **same plugin system** that you use in your webpack configuration!

content/concepts/targets.md

@@ -3,6 +3,7 @@ title: Targets
 sort: 10
 contributors:
   - TheLarkInn
+  - rouzbeh84
 ---
 
 Because JavaScript can be written for both server and browser, webpack offers multiple deployment _targets_ that you can set in your webpack [configuration](/configuration).