registry: use relative markdown links

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

docs/deploying.md

@@ -144,7 +144,7 @@ $ docker run -d \
 
 ### Customize the storage location
 
-By default, your registry data is persisted as a [docker volume](/storage/volumes.md)
+By default, your registry data is persisted as a [docker volume](../storage/volumes.md)
 on the host filesystem. If you want to store your registry contents at a specific
 location on your host filesystem, such as if you have an SSD or SAN mounted into
 a particular directory, you might decide to use a bind mount instead. A bind mount
@@ -262,13 +262,13 @@ certificate, this is for testing only. See [run an insecure registry](insecure.m
 
 ## Run the registry as a service
 
-[Swarm services](/engine/swarm/services.md) provide several advantages over
+[Swarm services](../engine/swarm/services.md) provide several advantages over
 standalone containers. They use a declarative model, which means that you define
 the desired state and Docker works to keep your service in that state. Services
 provide automatic load balancing scaling, and the ability to control the
 distribution of your service, among other advantages. Services also allow you to
 store sensitive data such as TLS certificates in
-[secrets](/engine/swarm/secrets.md).
+[secrets](../engine/swarm/secrets.md).
 
 The storage back-end you use determines whether you use a fully scaled service
 or a service with either only a single node or a node constraint.
@@ -560,6 +560,6 @@ More specific and advanced information is available in the following sections:
  - [Configuration reference](configuration.md)
  - [Working with notifications](notifications.md)
  - [Advanced "recipes"](recipes/index.md)
- - [Registry API](/registry/spec/api.md)
+ - [Registry API](spec/api.md)
  - [Storage driver model](storage-drivers/index.md)
  - [Token authentication](spec/auth/token.md)

docs/help.md

@@ -15,4 +15,4 @@ If you want to report a bug:
 - be sure to first read about [how to contribute](https://github.com/docker/distribution/blob/master/CONTRIBUTING.md).
 - you can then do so on the [GitHub project bugtracker](https://github.com/docker/distribution/issues).
 
-You can also find out more about the Docker's project [Getting Help resources](/opensource/get-help.md).
+You can also find out more about the Docker's project [Getting Help resources](../opensource/ways.md).

docs/insecure.md

@@ -95,11 +95,11 @@ This is more secure than the insecure registry solution.
 
 
     - **Docker Desktop for Mac**: Follow the instructions on
-      [Adding custom CA certificates](/docker-for-mac/faqs.md#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"}.
+      [Adding custom CA certificates](../docker-for-mac/faqs.md#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"}.
       Restart Docker.
 
     - **Docker Desktop for Windows**: Follow the instructions on
-      [Adding custom CA certificates](/docker-for-windows/faqs.md#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"}.
+      [Adding custom CA certificates](../docker-for-windows/faqs.md#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"}.
       Restart Docker.
 
 

docs/introduction.md

@@ -39,7 +39,7 @@ Image names as used in typical docker commands reflect their origin:
  * `docker pull myregistrydomain:port/foo/bar` instructs docker to contact the registry located at `myregistrydomain:port` to find the image `foo/bar`
 
 You can find out more about the various Docker commands dealing with images in
-the [official Docker engine documentation](/engine/reference/commandline/cli.md).
+the [official Docker engine documentation](../engine/reference/commandline/cli.md).
 
 ## Use cases
 

docs/recipes/apache.md

@@ -30,7 +30,7 @@ Furthermore, introducing an extra http layer in your communication pipeline adds
 
 ## Setting things up
 
-Read again [the requirements](/registry/recipes/index.md#requirements).
+Read again [the requirements](index.md#requirements).
 
 Ready?
 

docs/recipes/mirror.md

@@ -88,12 +88,12 @@ proxy:
 
 > **Warning**: For the scheduler to clean up old entries, `delete` must
 > be enabled in the registry configuration. See
-> [Registry Configuration](/registry/configuration.md) for more details.
+> [Registry Configuration](../configuration.md) for more details.
 
 ### Configure the Docker daemon
 
 Either pass the `--registry-mirror` option when starting `dockerd` manually,
-or edit [`/etc/docker/daemon.json`](/engine/reference/commandline/dockerd.md#daemon-configuration-file)
+or edit [`/etc/docker/daemon.json`](../../engine/reference/commandline/dockerd.md#daemon-configuration-file)
 and add the `registry-mirrors` key and value, to make the change persistent.
 
 ```json

docs/recipes/nginx.md

@@ -74,7 +74,7 @@ properly. For more information, see
 
 ## Setting things up
 
-Review the [requirements](/registry/recipes/index.md#requirements), then follow these steps.
+Review the [requirements](index.md#requirements), then follow these steps.
 
 1.  Create the required directories
 

docs/recipes/osx-setup-guide.md

@@ -12,7 +12,7 @@ This is useful if you intend to run a registry server natively on macOS.
 
 You can start a VM on macOS, and deploy your registry normally as a container using Docker inside that VM.
 
-The simplest road to get there is traditionally to use the [docker Toolbox](https://www.docker.com/toolbox), or [docker-machine](/machine/index.md), which usually relies on the [boot2docker](http://boot2docker.io/) ISO inside a VirtualBox VM.
+The simplest road to get there is traditionally to use the [docker Toolbox](https://www.docker.com/toolbox), or [docker-machine](../../machine/index.md), which usually relies on the [boot2docker](http://boot2docker.io/) ISO inside a VirtualBox VM.
 
 ### Solution