Enabled GitHub Flavored Markdown

GitHub flavored markdown is now supported for links and images. Also, ran LinkChecker and FileResolver. Yay!
Fixes from Spider check
Output for docker/docker now goes into engine directory

Signed-off-by: Mary Anthony <mary@docker.com>
Upstream-commit: 8fee1c2020186ac100b45e64864b94ae3a169ad5
Component: engine

components/engine/docs/examples/apt-cacher-ng.md

@@ -10,10 +10,11 @@ parent = "smn_applied"
 
 # Dockerizing an apt-cacher-ng service
 
-> **Note**: **If you don't like sudo** then see [*Giving non-root
-> access*](/installation/binaries/#giving-non-root-access).
-> **If you're using OS X or Docker via TCP** then you shouldn't use
-> sudo.
+> **Note**: 
+> - **If you don't like sudo** then see [*Giving non-root
+>   access*](../installation/binaries.md#giving-non-root-access).
+> - **If you're using OS X or docker via TCP** then you shouldn't use
+>   sudo.
 
 When you have multiple Docker servers, or build unrelated Docker
 containers which can't make use of the Docker build cache, it can be

components/engine/docs/examples/couchdb_data_volumes.md

@@ -10,8 +10,9 @@ parent = "smn_applied"
 
 # Dockerizing a CouchDB service
 
-> **Note**: **If you don't like sudo** then see [*Giving non-root
-> access*](/installation/binaries/#giving-non-root-access)
+> **Note**: 
+> - **If you don't like sudo** then see [*Giving non-root
+>   access*](../installation/binaries.md#giving-non-root-access)
 
 Here's an example of using data volumes to share the same data between
 two CouchDB containers. This could be used for hot upgrades, testing

components/engine/docs/examples/index.md

@@ -14,10 +14,10 @@ weight = 8
 
 This section contains the following:
 
-* [Dockerizing MongoDB](/examples/mongodb/)
-* [Dockerizing PostgreSQL](/examples/postgresql_service/)    
-* [Dockerizing a CouchDB service](/examples/couchdb_data_volumes/)         
-* [Dockerizing a Node.js web app](/examples/nodejs_web_app/)
-* [Dockerizing a Redis service](/examples/running_redis_service/)
-* [Dockerizing an apt-cacher-ng service](/examples/apt-cacher-ng/)
-* [Dockerizing applications: A 'Hello world'](/userguide/dockerizing)
+* [Dockerizing MongoDB](mongodb.md)
+* [Dockerizing PostgreSQL](postgresql_service.md)    
+* [Dockerizing a CouchDB service](couchdb_data_volumes.md)         
+* [Dockerizing a Node.js web app](nodejs_web_app.md)
+* [Dockerizing a Redis service](running_redis_service.md)
+* [Dockerizing an apt-cacher-ng service](apt-cacher-ng.md)
+* [Dockerizing applications: A 'Hello world'](../userguide/dockerizing.md)

components/engine/docs/examples/mongodb.md

@@ -29,7 +29,7 @@ instances will bring several benefits, such as:
 > **Note:**
 >
 > If you do **_not_** like `sudo`, you might want to check out:
-> [*Giving non-root access*](/installation/binaries/#giving-non-root-access).
+> [*Giving non-root access*](../installation/binaries.md#giving-non-root-access).
 
 ## Creating a Dockerfile for MongoDB
 
@@ -172,6 +172,6 @@ the exposed port to two different ports on the host
     $ mongo --port 28001
     $ mongo --port 28002
 
- - [Linking containers](/userguide/dockerlinks)
- - [Cross-host linking containers](/articles/ambassador_pattern_linking/)
- - [Creating an Automated Build](/docker-io/builds/#automated-builds)
+ - [Linking containers](../userguide/dockerlinks.md)
+ - [Cross-host linking containers](../articles/ambassador_pattern_linking.md)
+ - [Creating an Automated Build](https://docs.docker.com/docker-hub/builds/)

components/engine/docs/examples/nodejs_web_app.md

@@ -10,12 +10,14 @@ parent = "smn_applied"
 
 # Dockerizing a Node.js web app
 
-> **Note**: **If you don't like sudo** then see [*Giving non-root
-> access*](/installation/binaries/#giving-non-root-access)
+> **Note**: 
+> - **If you don't like sudo** then see [*Giving non-root
+>   access*](../installation/binaries.md#giving-non-root-access)
 
-In this example, we are going to learn how to build a Docker image to run a
-simple Node.js "hello world" web application on CentOS. You can get the full source code at
-[https://github.com/enokd/docker-node-hello/](https://github.com/enokd/docker-node-hello/).
+The goal of this example is to show you how you can build your own
+Docker images from a parent image using a `Dockerfile`
+. We will do that by making a simple Node.js hello world web
+application running on CentOS. You can get the full source code at[https://github.com/enokd/docker-node-hello/](https://github.com/enokd/docker-node-hello/).
 
 ## Create Node.js app
 

components/engine/docs/examples/postgresql_service.md

@@ -10,8 +10,9 @@ parent = "smn_applied"
 
 # Dockerizing PostgreSQL
 
-> **Note**: **If you don't like sudo** then see [*Giving non-root
-> access*](/installation/binaries/#giving-non-root-access)
+> **Note**: 
+> - **If you don't like sudo** then see [*Giving non-root
+>   access*](../installation/binaries.md#giving-non-root-access)
 
 ## Installing PostgreSQL on Docker
 
@@ -84,7 +85,7 @@ And run the PostgreSQL server container (in the foreground):
     $ docker run --rm -P --name pg_test eg_postgresql
 
 There are 2 ways to connect to the PostgreSQL server. We can use [*Link
-Containers*](/userguide/dockerlinks), or we can access it from our host
+Containers*](../userguide/dockerlinks.md), or we can access it from our host
 (or the network).
 
 > **Note**: