docs(api): minor formatting and cleanup

Author: skipjack

src/content/api/loaders.md

@@ -21,16 +21,16 @@ A single result can be returned in **sync mode**. For multiple results the `this
 
 ```javascript
 module.exports = function(content) {
-    return someSyncOperation(content);
+  return someSyncOperation(content);
 };
 ```
 
 **sync-loader-with-multiple-results.js**
 
 ```javascript
 module.exports = function(content) {
-    this.callback(null, someSyncOperation(content), sourceMaps, ast);
-    return; // always return undefined when calling callback()
+  this.callback(null, someSyncOperation(content), sourceMaps, ast);
+  return; // always return undefined when calling callback()
 };
 ```
 

src/content/api/plugins.md

@@ -8,6 +8,21 @@ T> For a high-level introduction to writing plugins, start with [writing a plugi
 
 Many objects in webpack extend the `Tapable` class, which exposes a `plugin` method. And with the `plugin` method, plugins can inject custom build steps. You will see `compiler.plugin` and `compilation.plugin` used a lot. Essentially, each one of these plugin calls binds a callback to fire at specific steps throughout the build process.
 
+There are two types of plugin interfaces...
+
+__Timing Based__
+
+- sync (default): The plugin runs synchronously and returns its output.
+- async: The plugin runs asynchronously and uses the give `callback` to return its output.
+- parallel: The handlers are invoked in parallel.
+
+__Return Value__
+
+- not bailing (default): No return value.
+- bailing: The handlers are invoked in order until one handler returns something.
+- parallel bailing: The handlers are invoked in parallel (async). The first returned value (by order) is significant.
+- waterfall: Each handler gets the result value of the last handler as an argument.
+
 A plugin is installed once as webpack starts up. webpack installs a plugin by calling its `apply` method, and passes a reference to the webpack `compiler` object. You may then call `compiler.plugin` to access asset compilations and their individual build steps. An example would look like this:
 
 __my-plugin.js__
@@ -50,30 +65,12 @@ plugins: [
 ```
 
 
-## Plugin Interfaces
-
-There are two types of plugin interfaces.
-
-__Timing Based:__
-
-- sync (default): As seen above. Use return.
-- async: Last parameter is a callback. Signature: function(err, result)
-- parallel: The handlers are invoked parallel (async).
-
-__Return Value:__
-
-- not bailing (default): No return value.
-- bailing: The handlers are invoked in order until one handler returns something.
-- parallel bailing: The handlers are invoked in parallel (async). The first returned value (by order) is significant.
-- waterfall: Each handler gets the result value of the last handler as an argument.
-
-
-## Tapable & Tapable instances
+## Tapable & Tapable Instances
 
 The plugin architecture is mainly possible for webpack due to an internal library named `Tapable`.
 **Tapable Instances** are classes in the webpack source code which have been extended or mixed in from class `Tapable`.
 
 For plugin authors, it is important to know which are the `Tapable` instances in the webpack source code. These instances provide a variety of event hooks into which custom plugins can be attached.
 Hence, throughout this section are a list of all of the webpack `Tapable` instances (and their event hooks), which plugin authors can utilize.
 
-For more information on `Tapable` visit the [tapable repository](https://github.com/webpack/tapable) or visit the [complete overview](./tapable)
+For more information on `Tapable` visit the [complete overview](/api/tapable) or the [tapable repository](https://github.com/webpack/tapable).