Fix DDC broken links reported on docker#1068

datacenter/dtr/2.0/install/index.md

@@ -24,7 +24,7 @@ infrastructure has all the [requirements DTR needs to run](system-requirements.m
 
 Since DTR requires a Docker Universal Control Plane (UCP) cluster
 to run, you need to install UCP first.
-[Learn how to install UCP](/ucp/installation/install-production/). Make sure that the node you install DTR on is already joined to the UCP cluster.
+[Learn how to install UCP](/datacenter/ucp/1.1/installation/install-production.md). Make sure that the node you install DTR on is already joined to the UCP cluster.
 
 ## Step 3. Install DTR
 
@@ -37,7 +37,7 @@ To install DTR:
 
  Having a UCP client bundle allows you to run Docker commands on a UCP
  cluster.
- [Download a UCP client bundle](/ucp/access-ucp/cli-based-access/)
+ [Download a UCP client bundle](/datacenter/ucp/1.1/access-ucp/cli-based-access.md)
  and set up your CLI client to use it.
 
 2. Run the following command to install DTR.

datacenter/dtr/2.0/release-notes/prior-release-notes.md

@@ -132,7 +132,7 @@ documentation.
 
  * Users, depending on their roles, can access account information through the Trusted Registry UI.
 
- * View new API documentation through the Trusted Registry UI. You can also view this [documentation](/docker-trusted-registry/index.md) from Docker, Inc. docs section.
+ * View new API documentation through the Trusted Registry UI. You can also view this documentation from Docker, Inc. docs section.
 
 * New APIs
 
@@ -313,4 +313,4 @@ been disabled for DHE users because of these issues.
 ## Version 1.0.0
 (23 Apr 2015)
 
-- First release
+- First release

datacenter/install/aws.md

@@ -216,7 +216,7 @@ UCP. Then click on **Update**.
 7. Final step is to reconfigure DTR to use new UCP DNS and certificates.
 You need to run a `reconfigure` operation from the CLI. This step can be done
 from any Docker engine ( local or on the cloud) as long as you have
-UCP [client bundle](../datacenter/ucp/2.0/guides/access-ucp/cli-based-access.md).
+UCP [client bundle](../ucp/2.0/guides/access-ucp/cli-based-access.md).
 Once you download the bundle and load it, run the following command:
 
  ```
@@ -322,7 +322,7 @@ provides multiple advantages to easily deploy and access your application.
 #### Non-Swarm Mode Container Based Applications
 
 If you are deploying non-swarm mode container-based applications, you can
-follow [UCP docs](../datacenter/ucp/2.0/guides/applications/index.md) to
+follow [UCP docs](../ucp/2.0/guides/applications/index.md) to
 deploy your applications. Once you deploy your application on UCP, you can
 access them by using the specific worker node's public IP address and exposed
 port.

datacenter/install/linux.md

@@ -59,7 +59,7 @@ docker run --rm -it --name ucp \
 This runs the install command in interactive mode, so that you're prompted
 for any necessary configuration values.
 
-[Learn more about the UCP installation](../ucp/2.9/guides/installation/index.md)
+[Learn more about the UCP installation](../ucp/2.0/guides/installation/index.md)
 
 ### Step 4: License your installation
 

datacenter/ucp/1.1/install-sandbox-2.md

@@ -31,9 +31,9 @@ First, we'll set up a security exception that allows a the Docker-machine hosts
 used in your UCP cluster to push images to and pull images from DTR even though
 the DTR instance has a self-signed certificate. For a production deployment,
 you would
-[set up certificate trust](/ucp/configuration/dtr-integration/)
+[set up certificate trust](configuration/dtr-integration/)
 between UCP and DTR, and
-[between DTR and your Docker Engine](/docker-trusted-registry/repos-and-images/),
+between DTR and your Docker Engine/docker-trusted-registry/repos-and-images/,
 but for our sandbox deployment we can skip this.
 
 > **Warning**: These steps produce an insecure DTR connection. Do not use these

datacenter/ucp/1.1/installation/install-production.md

@@ -25,7 +25,7 @@ above to run. It is recommended to install the exact same version of the
 CS Docker Engine on all nodes.
 
 So on each host that you want to be part of the UCP cluster,
-[install CS Docker Engine 1.10.0 or above](/docker-trusted-registry/cs-engine/install/).
+[install CS Docker Engine 1.10.0 or above](/cs-engine/install.md).
 In the case where you are creating a VM template with CS Engine already
 installed, make sure that `/etc/docker/key.json` is not included in the image.
 You can do this by simply removing `/etc/docker/key.json`. You can then restart

index.md

@@ -90,23 +90,23 @@ title: Welcome to the Docs
 </li>
 <li>
 <div class="media_image">
- <a href="/docker-trusted-registry/"><img src="/images/icon-registry@2X.png" alt="Docker Trusted Registry"></a>
+ <a href="/datacenter/dtr/2.1/guides/index.md"><img src="/images/icon-registry@2X.png" alt="Docker Trusted Registry"></a>
 </div>
  <div class="media_content">
  <div data-mh="mh_docker_projects">
- <h3><a href="/docker-trusted-registry/">Docker Trusted Registry</a></h3>
+ <h3><a href="/datacenter/dtr/2.1/guides/index.md">Docker Trusted Registry</a></h3>
   <p>
  (DTR) stores and signs your images.</p>
  </div>
  </div>
 </li>
 <li>
 <div class="media_image">
- <a href="/ucp/overview/"><img src="/images/icon-ucp@2X.png" alt="Docker Universal Control Plane"></a>
+ <a href="/datacenter/ucp/2.0/guides/index.md"><img src="/images/icon-ucp@2X.png" alt="Docker Universal Control Plane"></a>
 </div>
  <div class="media_content">
  <div data-mh="mh_docker_projects">
- <h3><a href="/ucp/overview/">Docker Universal Control Plane</a></h3>
+ <h3><a href="/datacenter/ucp/2.0/guides/index.md">Docker Universal Control Plane</a></h3>
   <p>
  (UCP) Manage a cluster of on-premises Docker hosts as if they were a single machine.
  </p>
@@ -139,4 +139,4 @@ title: Welcome to the Docs
  </div>
 </li>
 </ul>
-</section>
+</section>