Update DTR urls

datacenter/dtr/2.3/guides/admin/backups-and-disaster-recovery.md

@@ -120,9 +120,9 @@ of the tar file created. The backup of the images should look like:
 ```none
 tar -tf {{ image_backup_file }}
 
-dtr-backup-v2.2.3/
-dtr-backup-v2.2.3/rethink/
-dtr-backup-v2.2.3/rethink/layers/
+dtr-backup-v{{ page.dtr_version_patch }}/
+dtr-backup-v{{ page.dtr_version_patch }}/rethink/
+dtr-backup-v{{ page.dtr_version_patch }}/rethink/layers/
 ```
 
 And the backup of the DTR metadata should look like:
@@ -131,10 +131,10 @@ And the backup of the DTR metadata should look like:
 tar -tf {{ backup-metadata.tar }}
 
 # The archive should look like this
-dtr-backup-v2.2.1/
-dtr-backup-v2.2.1/rethink/
-dtr-backup-v2.2.1/rethink/properties/
-dtr-backup-v2.2.1/rethink/properties/0
+dtr-backup-v{{ page.dtr_version_patch }}/
+dtr-backup-v{{ page.dtr_version_patch }}/rethink/
+dtr-backup-v{{ page.dtr_version_patch }}/rethink/properties/
+dtr-backup-v{{ page.dtr_version_patch }}/rethink/properties/0
 ```
 
 If you've encrypted the metadata backup, you can use:

datacenter/dtr/2.3/guides/admin/configure/external-storage/s3.md

@@ -106,4 +106,4 @@ of both DTR and the storage backend, they won't be able to push or pull images.
 And if you've configured DTR to skip TLS verification, you also need to
 configure all Docker Engines that push or pull from DTR to skip TLS
 verification. You do this by adding DTR to
-the [list of insecure registries when starting Docker](https://docs.docker.com/engine/reference/commandline/dockerd/).
+the [list of insecure registries when starting Docker](/engine/reference/commandline/dockerd.md).

datacenter/dtr/2.3/guides/admin/configure/use-a-load-balancer.md

@@ -58,7 +58,7 @@ the health of every replica in a cluster, querying each replica individiually is
 the preferred way to do it in real time.
 
 The `/api/v0/meta/cluster_status`
-[endpoint](https://docs.docker.com/datacenter/dtr/2.2/reference/api/)
+[endpoint](../../../reference/api)
 returns a JSON object for the entire cluster *as observed* by the replica being
 queried, and it takes the form:
 

datacenter/dtr/2.3/guides/admin/install/index.md

@@ -19,7 +19,7 @@ infrastructure has all the [requirements DTR needs to run](system-requirements.m
 
 Since DTR requires Docker Universal Control Plane (UCP)
 to run, you need to install UCP on all the nodes where you plan to install DTR.
-[Learn how to install UCP](/datacenter/ucp/2.1/guides/admin/install.md).
+[Learn how to install UCP](/datacenter/ucp/2.2/guides/admin/install.md).
 
 DTR needs to be installed on a worker node that is being managed by UCP.
 You can't install DTR on a standalone Docker Engine.
@@ -135,4 +135,4 @@ To add replicas to a DTR cluster, use the `docker/dtr join` command:
 ## See also
 
 * [Install DTR offline](install-offline.md)
-* [Upgrade DTR](../upgrade/index.md)
+* [Upgrade DTR](../upgrade.md)

datacenter/dtr/2.3/guides/admin/upgrade.md

@@ -38,13 +38,12 @@ to ensure the impact on your business is close to none.
 ## Minor upgrade
 
 Before starting your upgrade planning, make sure that the version of UCP you are
-using is supported by the version of DTR you are trying to upgrade to. <!--(TODO:
-link to the compatibility matrix)-->
+using is supported by the version of DTR you are trying to upgrade to.
 
 > Backup DTR before upgrading
 >
 > Before performing any upgrade it’s important to backup. See
-> [DTR backups and recovery](/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery.md).
+> [DTR backups and recovery](backups-and-disaster-recovery.md).
 
 ### Step 1. Upgrade DTR to 2.2 if necessary
 
@@ -59,7 +58,7 @@ $ docker pull docker/dtr:{{ page.dtr_version_patch }}
 ```
 
 If the node you're upgrading doesn't have access to the internet, you can
-follow the [offline installation documentation](../install/install-offline.md)
+follow the [offline installation documentation](install/install-offline.md)
 to get the images.
 
 Once you have the latest image on your machine (and the images on the target

datacenter/dtr/2.3/guides/index.md

@@ -30,10 +30,10 @@ and metadata such that if a machine fails, DTR continues to operate and can be r
 
 ## Efficiency
 
-DTR has the ability to [cache images closer to users](https://docs.docker.com/datacenter/dtr/2.2/guides/admin/configure/deploy-caches/)
+DTR has the ability to [cache images closer to users](../admin/configure/deploy-caches/index.md)
 to reduce the amount of bandwidth used during docker pulls.
 
-DTR has the ability to [clean up unreferenced manifests and layers](https://docs.docker.com/datacenter/dtr/2.2/guides/admin/configure/garbage-collection/).
+DTR has the ability to [clean up unreferenced manifests and layers](../configure/garbage-collection.md).
 
 ## Built-in access control
 

datacenter/dtr/2.3/guides/user/access-dtr/configure-your-notary-client.md

@@ -102,7 +102,7 @@ repository.
 
 The last step in configuring the Notary CLI client is to import the private
 key of your UCP client bundle.
-[Get a new client bundle if you don't have one yet](/datacenter/ucp/2.1/guides/user/access-ucp/cli-based-access.md).
+[Get a new client bundle if you don't have one yet](/datacenter/ucp/2.2/guides/user/access-ucp/cli-based-access.md).
 
 Import the private key in your UCP bundle into the Notary CLI client:
 

datacenter/dtr/2.3/guides/user/manage-images/sign-images/delegate-image-signing.md

@@ -39,7 +39,7 @@ The member of the IT ops team then asks the QA team for their public key
 certificate files that are part of their UCP client bundle.
 
 If they don't have a UCP client bundle,
-[they can download a new one](/datacenter/ucp/2.1/guides/user/access-ucp/cli-based-access.md).
+[they can download a new one](/datacenter/ucp/2.2/guides/user/access-ucp/cli-based-access.md).
 
 ## Delegate image signing