docs: fix broken output related links

Author: skipjack

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.
+Configuring the `output` configuration 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.
 
 
 ## Usage
@@ -35,7 +35,7 @@ This configuration would output a single `bundle.js` file into the `/home/proj/p
 
 ## Multiple Entry Points
 
-If your configuration creates more than a single "chunk" (as with multiple entry points or when using plugins like CommonsChunkPlugin), you should use [substitutions](/config/output#output-filename) to ensure that each file has a unique name.
+If your configuration creates more than a single "chunk" (as with multiple entry points or when using plugins like CommonsChunkPlugin), you should use [substitutions](/configuration/output#output-filename) to ensure that each file has a unique name.
 
 ```javascript
 {

content/guides/caching.md

@@ -34,8 +34,7 @@ application.js?build=1
 application.css?build=1
 ```
 
-It is even easier to do with webpack. Each webpack build generates a unique hash which can be used to compose a filename, by including output [placeholders](/concepts/output/#options).
-The following example config will generate 2 files (1 per entry) with hashes in filenames:
+It is even easier to do with webpack. Each webpack build generates a unique hash which can be used to compose a filename, by including output [substitutions](/configuration/output#output-filename). The following example config will generate 2 files (1 per entry) with hashes in filenames:
 
 ```js
 // webpack.config.js