docs(api) Fix markdown lint errors

Author: montogeek

src/content/api/compiler-hooks.md

@@ -7,7 +7,7 @@ contributors:
 ---
 
 The `Compiler` module is the main engine that creates a compilation instance
-with all the options passed through the [CLI]() or [Node API](). It extends the
+with all the options passed through the [CLI](/api/cli) or [Node API](/api/node). It extends the
 `Tapable` class in order to register and call plugins. Most user facing plugins
 are first registered on the `Compiler`.
 

src/content/api/node.md

@@ -282,9 +282,9 @@ like [parallel-webpack](https://www.npmjs.com/package/parallel-webpack).
 
 For a good error handling, you need to account for these three types of errors:
 
-* Fatal webpack errors (wrong configuration, etc)
-* Compilation errors (missing modules, syntax errors, etc)
-* Compilation warnings
+- Fatal webpack errors (wrong configuration, etc)
+- Compilation errors (missing modules, syntax errors, etc)
+- Compilation warnings
 
 Here’s an example that does all that:
 

src/content/api/parser.md

@@ -9,7 +9,7 @@ being processed by webpack. The `parser` is yet another webpack class that
 extends `tapable` and provides a variety of `tapable` hooks that can be used by
 plugin authors to customize the parsing process.
 
-The `parser` is found within [module factories]() and therefore takes little
+The `parser` is found within [module factories](/api/module-factories/) and therefore takes little
 more work to access:
 
 ``` js

src/content/api/plugins.md

@@ -10,7 +10,7 @@ contributors:
 
 Plugins are a key piece of the webpack ecosystem and provide the community with
 a powerful way to tap into webpack's compilation process. A plugin is able to
-[hook]() into key events that are fired throughout each compilation. Every step
+[hook](/api/compiler/#event-hooks) into key events that are fired throughout each compilation. Every step
 of the way, the plugin will have full access to the `compiler` and, when
 applicable, the current `compilation`.
 
@@ -41,7 +41,7 @@ noted.
 Depending on the hooks used and `tap` methods applied, plugins can function in
 a number of different ways. The way this works is closely related to the
 [hooks](https://github.com/webpack/tapable#tapable) provided by `Tapable`. The
-[compiler hooks]() each note the underlying `Tapable` hook indicating which
+[compiler hooks](/api/compiler/#event-hooks) each note the underlying `Tapable` hook indicating which
 `tap` methods are available.
 
 So depending which event you `tap` into, the plugin may run differently. For
@@ -90,11 +90,11 @@ compiler.hooks.myCustomHook = new SyncHook(['a', 'b', 'c'])
 compiler.hooks.myCustomHook.call(a, b, c);
 ```
 
-Again, see the [documentation]() for `tapable` to learn more about the
+Again, see the [documentation](/api/tapable/) for `tapable` to learn more about the
 different hook classes and how they work.
 
 
 ## Next Steps
 
-See the [compiler hooks]() section for a detailed listing of all the available
+See the [compiler hooks](/api/compiler/#event-hooks) section for a detailed listing of all the available
 `compiler` hooks and the parameters they make available.

src/content/api/resolvers.md

@@ -7,11 +7,11 @@ sort: 3
 Resolvers are created using the `enhanced-resolve` package. The `Resolver`
 class extends the `tapable` class and uses `tapable` to provide a few hooks.
 The `enhanced-resolve` package can be used directly to create new resolvers,
-however any [`compiler` instance]() has a few resolver instances that can be
+however any [`compiler` instance](/api/compiler/) has a few resolver instances that can be
 tapped into.
 
 Before reading on, make sure you at least skim through the
-[`enhanced-resolve`]() and [`tapable`]() documentation.
+[`enhanced-resolve`](https://github.com/webpack/enhanced-resolve) and [`tapable`](/api/tapable/) documentation.
 
 
 ## Types
@@ -39,14 +39,14 @@ Where `[type]` is one of the three resolvers mention above, specified as:
 - `context`
 - `loader`
 
-See the `enhanced-resolve` [documentation]() for a full list of hooks and
+See the `enhanced-resolve` [documentation](https://github.com/webpack/enhanced-resolve) for a full list of hooks and
 descriptions.
 
 
 ## Configuration Options
 
 The resolvers mentioned above can also be customized via a configuration file
-with the [`resolve`]() or [`resolveLoader`]() options. These options allow
+with the [`resolve`](/configuration/resolve/) or [`resolveLoader`](/configuration/resolve/#resolveloader) options. These options allow
 users to change the resolving behavior through a variety of options including
 through resolve `plugins`.