Looking into some broken links, I noticed that we don't need to use

relative paths, and also fixed some broken images.

There are still more todo - next PR I think :)

Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@fosiki.com> (github: SvenDowideit)

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

@@ -9,7 +9,7 @@ page_keywords: API, Docker, rcli, REST, documentation
  - 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).
+   /use/basics/#bind-docker).
  - 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`
@@ -540,7 +540,7 @@ Attach to the container `id`
 
     When using the TTY setting is enabled in
     [`POST /containers/create`
-    ](../../docker_remote_api_v1.9/#post--containers-create "POST /containers/create"),
+    ](/api/docker_remote_api_v1.9/#post--containers-create "POST /containers/create"),
     the stream is the raw data from the process PTY and client's stdin.
     When the TTY is disabled, then the stream is multiplexed to separate
     stdout and stderr.

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

@@ -9,7 +9,7 @@ page_keywords: API, Docker, rcli, REST, documentation
  - 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).
+   /use/basics/#bind-docker).
  - 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`
@@ -489,7 +489,7 @@ Attach to the container `id`
 
     When using the TTY setting is enabled in
     [`POST /containers/create`
-    ](../../docker_remote_api_v1.9/#post--containers-create "POST /containers/create"),
+    ](/api/docker_remote_api_v1.9/#post--containers-create "POST /containers/create"),
     the stream is the raw data from the process PTY and client's stdin.
     When the TTY is disabled, then the stream is multiplexed to separate
     stdout and stderr.
@@ -980,7 +980,7 @@ Build an image from Dockerfile via stdin
     The archive must include a file called `Dockerfile`
     at its root. It may include any number of other files,
     which will be accessible in the build context (See the [*ADD build
-    command*](../../../builder/#dockerbuilder)).
+    command*](/builder/#dockerbuilder)).
 
     Query Parameters:
 

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

@@ -9,7 +9,7 @@ page_keywords: API, Docker, rcli, REST, documentation
  - 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).
+   /use/basics/#bind-docker).
  - 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`
@@ -531,7 +531,7 @@ Attach to the container `id`
 
     When using the TTY setting is enabled in
     [`POST /containers/create`
-    ](../../docker_remote_api_v1.9/#post--containers-create "POST /containers/create"),
+    ](/api/docker_remote_api_v1.9/#post--containers-create "POST /containers/create"),
     the stream is the raw data from the process PTY and client's stdin.
     When the TTY is disabled, then the stream is multiplexed to separate
     stdout and stderr.
@@ -1024,7 +1024,7 @@ Build an image from Dockerfile via stdin
     The archive must include a file called `Dockerfile`
     at its root. It may include any number of other files,
     which will be accessible in the build context (See the [*ADD build
-    command*](../../../builder/#dockerbuilder)).
+    command*](/reference/builder/#dockerbuilder)).
 
     Query Parameters:
 

docs/sources/reference/api/docker_io_oauth_api.md

@@ -96,7 +96,7 @@ an Authorization Code.
     prompt which asks the user to authorize your application with a
     description of the requested scopes.
 
-    ![](../../../static_files/io_oauth_authorization_page.png)
+    ![](/reference/api/_static/io_oauth_authorization_page.png)
 
     Once the user allows or denies your Authorization Request the user
     will be redirected back to your application. Included in that

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

@@ -9,7 +9,7 @@ page_keywords: API, Docker, rcli, REST, documentation
  - 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).
+   /use/basics/#bind-docker).
  - 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`
@@ -1009,7 +1009,7 @@ Build an image from Dockerfile via stdin
     The archive must include a file called `Dockerfile`
  at its root. It may include any number of other files,
     which will be accessible in the build context (See the [*ADD build
-    command*](../../builder/#dockerbuilder)).
+    command*](/reference/builder/#dockerbuilder)).
 
     Query Parameters:
 

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

@@ -9,7 +9,7 @@ page_keywords: API, Docker, rcli, REST, documentation
  - 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).
+   /use/basics/#bind-docker).
  - 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`
@@ -1012,7 +1012,7 @@ Build an image from Dockerfile via stdin
     The archive must include a file called `Dockerfile`
     at its root. It may include any number of other files,
     which will be accessible in the build context (See the [*ADD build
-    command*](../../builder/#dockerbuilder)).
+    command*](/reference/builder/#dockerbuilder)).
 
     Query Parameters:
 

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

@@ -9,7 +9,7 @@ page_keywords: API, Docker, rcli, REST, documentation
  - 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).
+   /use/basics/#bind-docker).
  - 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`
@@ -1022,7 +1022,7 @@ Build an image from Dockerfile using a POST body.
     The archive must include a file called `Dockerfile`
  at its root. It may include any number of other files,
     which will be accessible in the build context (See the [*ADD build
-    command*](../../builder/#dockerbuilder)).
+    command*](/reference/builder/#dockerbuilder)).
 
     Query Parameters:
 

docs/sources/reference/api/registry_index_spec.md

@@ -95,7 +95,7 @@ supports:
 
 ### Pull
 
-![](../../../static_files/docker_pull_chart.png)
+![](/static_files/docker_pull_chart.png)
 
 1.  Contact the Index to know where I should download “samalba/busybox”
 2.  Index replies: a. `samalba/busybox` is on Registry A b. here are the
@@ -187,7 +187,7 @@ and for an active account.
 
 ### Push
 
-![](../../../static_files/docker_push_chart.png)
+![](/static_files/docker_push_chart.png)
 
 1.  Contact the index to allocate the repository name “samalba/busybox”
     (authentication required with user credentials)