Adding User Guide

* Added User Guide section outlines.
* Added User Guide to menu.
* Moved HTTPS example to articles.
* Replaced Hello World example with User Guide.
* Moved use cases out of examples.
* Updated Introduction to add User Guide.
* Redirected migrated /use and /articles links.
* Added Docker.io section
* Added Dockerized section
* Added Using Docker section
* Added Docker Images section
* Added Docker Links section
* Added Docker Volumes section

Docker-DCO-1.1-Signed-off-by: James Turnbull <james@lovedthanlost.net> (github: jamtur01)

docs/sources/reference/api/docker_remote_api_v1.10.md

@@ -7,9 +7,8 @@ page_keywords: API, Docker, rcli, REST, documentation
 ## 1. Brief introduction
 
  - The Remote API has replaced rcli
- - The daemon listens on `unix:///var/run/docker.sock` but you can
-   [*Bind Docker to another host/port or a Unix socket*](
-   /use/basics/#bind-docker).
+ - The daemon listens on `unix:///var/run/docker.sock` but you can bind
+   Docker to another host/port or a Unix socket.
  - The API tends to be REST, but for some complex commands, like `attach`
    or `pull`, the HTTP connection is hijacked to transport `stdout, stdin`
    and `stderr`

docs/sources/reference/api/docker_remote_api_v1.11.md

@@ -7,9 +7,8 @@ page_keywords: API, Docker, rcli, REST, documentation
 ## 1. Brief introduction
 
  - The Remote API has replaced rcli
- - The daemon listens on `unix:///var/run/docker.sock` but you can
-   [*Bind Docker to another host/port or a Unix socket*](
-   /use/basics/#bind-docker).
+ - The daemon listens on `unix:///var/run/docker.sock` but you can bind
+   Docker to another host/port or a Unix socket.
  - The API tends to be REST, but for some complex commands, like `attach`
    or `pull`, the HTTP connection is hijacked to transport `stdout, stdin`
    and `stderr`

docs/sources/reference/api/docker_remote_api_v1.6.md

@@ -7,9 +7,8 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
  - The Remote API has replaced rcli
- - The daemon listens on `unix:///var/run/docker.sock` but you can
-   [*Bind Docker to another host/port or a Unix socket*](
-   /use/basics/#bind-docker).
+ - The daemon listens on `unix:///var/run/docker.sock` but you can bind
+   Docker to another host/port or a Unix socket.
  - The API tends to be REST, but for some complex commands, like `attach`
    or `pull`, the HTTP connection is hijacked to transport `stdout, stdin`
    and `stderr`

docs/sources/reference/api/docker_remote_api_v1.7.md

@@ -7,9 +7,8 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
  - The Remote API has replaced rcli
- - The daemon listens on `unix:///var/run/docker.sock` but you can
-   [*Bind Docker to another host/port or a Unix socket*](
-   /use/basics/#bind-docker).
+ - The daemon listens on `unix:///var/run/docker.sock` but you can bind
+   Docker to another host/port or a Unix socket.
  - The API tends to be REST, but for some complex commands, like `attach`
    or `pull`, the HTTP connection is hijacked to transport `stdout, stdin`
    and `stderr`

docs/sources/reference/api/docker_remote_api_v1.8.md

@@ -7,9 +7,8 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
  - The Remote API has replaced rcli
- - The daemon listens on `unix:///var/run/docker.sock` but you can
-   [*Bind Docker to another host/port or a Unix socket*](
-   /use/basics/#bind-docker).
+ - The daemon listens on `unix:///var/run/docker.sock` but you can bind
+   Docker to another host/port or a Unix socket.
  - The API tends to be REST, but for some complex commands, like `attach`
    or `pull`, the HTTP connection is hijacked to transport `stdout, stdin`
    and `stderr`

docs/sources/reference/api/docker_remote_api_v1.9.md

@@ -7,9 +7,8 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
  - The Remote API has replaced rcli
- - The daemon listens on `unix:///var/run/docker.sock` but you can
-   [*Bind Docker to another host/port or a Unix socket*](
-   /use/basics/#bind-docker).
+ - The daemon listens on `unix:///var/run/docker.sock` but you can bind
+   Docker to another host/port or a Unix socket.
  - The API tends to be REST, but for some complex commands, like `attach`
    or `pull`, the HTTP connection is hijacked to transport `stdout, stdin`
    and `stderr`