Update some screenshots for DDC (#1894)

* Update screenshots for /datacenter/install/aws/

* Update screenshots for datacenter/install/linux/

* Update screenshots for datacenter/ucp/2.1/guides/

* Update screenshots for datacenter/ucp/2.1/guides/admin/install/

* Update screenshots for datacenter/ucp/2.1/guides/admin/configure/scale-your-cluster/

* Fix screenshot's text in /ucp/2.1/guides/admin/install/

* Update screenshots for datacenter/ucp/2.1/guides/admin/configure/scale-your-cluster/

* Update screenshots for /datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/

* Update screenshot for /datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs/

* Update screenshot for /datacenter/ucp/2.1/guides/user/access-ucp/

* Update screenshots for /datacenter/ucp/2.1/guides/user/services/

* Update screenshots for /datacenter/ucp/2.1/guides/user/secrets/

* Update screenshots for /datacenter/install/aws/

* Update screenshots for datacenter/install/linux/

* Update screenshots for datacenter/ucp/2.1/guides/

* Update screenshots for datacenter/ucp/2.1/guides/admin/install/

* Update screenshots for datacenter/ucp/2.1/guides/admin/configure/scale-your-cluster/

* Fix screenshot's text in /ucp/2.1/guides/admin/install/

* Update screenshots for datacenter/ucp/2.1/guides/admin/configure/scale-your-cluster/

* Update screenshots for /datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/

* Update screenshot for /datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs/

* Update screenshot for /datacenter/ucp/2.1/guides/user/access-ucp/

* Update screenshots for /datacenter/ucp/2.1/guides/user/services/

* Update screenshots for /datacenter/ucp/2.1/guides/user/secrets/

datacenter/install/aws.md

@@ -128,11 +128,11 @@ above configuration options.
 
 - Click on **Launch Stack** below. This link will take you to AWS cloudformation portal.
 
-	[![Docker Datacenter on Docker for AWS](https://s3.amazonaws.com/cloudformation-examples/cloudformation-launch-stack.png)]({{ launch_url }}{{ template_url }})
+	[![Docker Datacenter on Docker for AWS](https://s3.amazonaws.com/cloudformation-examples/cloudformation-launch-stack.png)]({{ launch_url }}{{ template_url }}){: .with-border}
 
 - Confirm your AWS Region that you'd like to launch this stack in (top right corner)
 - Provide the required parameters and click **Next** (see below)
-![console_installation.png](../images/console_installation.png)
+![console_installation.png](../images/console_installation.png){: .with-border}
 - **Confirm** and **Launch**
 - Once the stack is successfully created (it does take between 10-15 mins), click on **Output** tab to see the URLs of UCP and DTR.
 
@@ -214,15 +214,16 @@ which is a highly optimized AMI built specifically for running Docker on AWS
 Once the stack is successfully created, you can access UCP and DTR URLs in the
 output tab as follows:
 
-![insecure.png](../images/output.png)
+![insecure.png](../images/output.png){: .with-border}
 
 When accessing UCP and DTR, log in using the username and password that you
 provided when you launched the cloudformation stack. You should see the below
 landing pages:
 
 
-![ucp.png](../images/ucp.png)
+![ucp.png](../images/ucp.png){: .with-border}
-![dtr.png](../images/dtr.png)
+
+![dtr.png](../images/dtr.png){: .with-border}
 
 > Note: During the installation process, a self-signed certificate is generated
 for both UCP and DTR. You can replace these certificates with your own
@@ -302,11 +303,11 @@ provides multiple advantages to easily deploy and access your application.
     ```
     b. Notice the updated ELB configuration:
 
-    ![elb_listeners_update.png](../images/elb_listeners_update.png)
+    ![elb_listeners_update.png](../images/elb_listeners_update.png){: .with-border}
 
     c. Access your application using **DefaultExternalTarget** DNS and published port:
 
-    ![app.png](../images/app.png)
+    ![app.png](../images/app.png){: .with-border}
 
 
 2.  **Swarm Mode Routing Mesh**
@@ -382,12 +383,12 @@ created when filling out the CloudFormation template for Docker for AWS.
 Once you find it, click the checkbox, next to the name. Then Click on the
 "Edit" button on the lower detail pane.
 
-![console_installation.png](../images/autoscale_update.png)
+![console_installation.png](../images/autoscale_update.png){: .with-border}
 
 Change the "Desired" field to the size of the worker pool that you would like,
 and hit "Save".
 
-![console_installation.png](../images/autoscale_save.png)
+![console_installation.png](../images/autoscale_save.png){: .with-border}
 
 This will take a few minutes and add the new workers to your swarm
 automatically. To lower the number of workers back down, you just need to
@@ -399,7 +400,7 @@ Go to the CloudFormation management page, and click the checkbox next to the
 stack you want to update. Then Click on the action button at the top, and
 select "Update Stack".
 
-![console_installation.png](../images/cloudformation_update.png)
+![console_installation.png](../images/cloudformation_update.png){: .with-border}
 
 Pick "Use current template", and then click "Next". Fill out the same parameters
 you have specified before, but this time, change your worker count to the new

datacenter/ucp/2.1/guides/admin/configure/scale-your-cluster.md

@@ -9,7 +9,7 @@ Docker UCP is designed for scaling horizontally as your applications grow in
 size and usage. You can add or remove nodes from the UCP cluster to make it
 scale to your needs.
 
-![](../../images/scale-your-cluster-1.svg)
+![](../../images/scale-your-cluster-0.svg)
 
 Since UCP leverages the clustering functionality provided by Docker Engine,
 you use the [docker swarm join](/engine/swarm/swarm-tutorial/add-nodes.md)
@@ -47,7 +47,7 @@ the **Resources** page, and go to the **Nodes** section.
 
 Click the **Add Node button** to add a new node.
 
-![](../../images/scale-your-cluster-2.png){: .with-border}
+![](../../../../../images/try-ddc-3.png){: .with-border}
 
 Check the 'Add node as a manager' option if you want to add the node as manager.
 Also, set the 'Use a custom listen address' option to specify the IP of the
@@ -56,7 +56,7 @@ host that you'll be joining to the cluster.
 Then you can copy the command displayed, use ssh to **log into the host** that
 you want to join to the cluster, and **run the command** on that host.
 
-![](../../images/scale-your-cluster-3.png){: .with-border}
+![](../../images/scale-your-cluster-2.png){: .with-border}
 
 After you run the join command in the node, the node starts being displayed
 in UCP.
@@ -96,7 +96,7 @@ so that it is:
 * Drained: the node won't receive new tasks. Existing tasks are stopped and
 replica tasks are launched in active nodes.
 
-![](../../images/scale-your-cluster-4.png){: .with-border}
+![](../../images/scale-your-cluster-3.png){: .with-border}
 
 If you're load-balancing user requests to UCP across multiple manager nodes,
 when demoting those nodes into workers, don't forget to remove them from your

datacenter/ucp/2.1/guides/admin/install/index.md

@@ -82,7 +82,7 @@ Now that UCP is installed, you need to license it. In your browser, navigate
 to the UCP web UI, login with your administrator credentials and upload your
 license.
 
-![](../../images/install-production-1.png){: .with-border}
+![](../../../../../images/try-ddc-1.png){: .with-border}
 
 If you're registered in the beta program and don't have a license yet, you
 can get it from your [Docker Store subscriptions](https://store.docker.com/?overlay=subscriptions).
@@ -101,11 +101,11 @@ for worker nodes to execute.
 To join manager nodes to the swarm, go to the **UCP web UI**, navigate to
 the **Resources** page, and go to the **Nodes** section.
 
-![](../../images/install-production-2.png){: .with-border}
+![](../../images/step-6-one-node.png){: .with-border}
 
 Click the **Add Node button** to add a new node.
 
-![](../../images/install-production-3.png){: .with-border}
+![](../../../../../images/try-ddc-3.png){: .with-border}
 
 Check the 'Add node as a manager' to turn this node into a manager and replicate
 UCP for high-availability.
@@ -119,7 +119,7 @@ can reach it.
 For each manager node that you want to join to UCP, login into that
 node using ssh, and run the join command that is displayed on UCP.
 
-![](../../images/install-production-4.png){: .with-border}
+![](../../images/step-6-two-nodes.png){: .with-border}
 
 After you run the join command in the node, the node starts being displayed
 in UCP.

datacenter/ucp/2.1/guides/index.md

@@ -10,7 +10,7 @@ solution from Docker. You install it on-premises or in your virtual private
 cloud, and it helps you manage your Docker cluster and applications from a
 single place.
 
-![](images/overview-1.png){: .with-border}
+![](../../../images/ucp.png){: .with-border}
 
 ## Centralized cluster management
 
@@ -21,7 +21,7 @@ by Docker to make it easier to manage your cluster from a centralized place.
 
 You can manage and monitor your container cluster using a graphical UI.
 
-![](images/overview-2.png){: .with-border}
+![](../../../images/try-ddc-2.png){: .with-border}
 
 Since UCP exposes the standard Docker API, you can continue using the tools
 you already know, including the Docker CLI client, to deploy and manage your

datacenter/ucp/2.1/guides/user/access-ucp/index.md

@@ -7,7 +7,7 @@ title: Web-based access
 Docker Universal Control Plane allows you to manage your cluster in a visual
 way, from your browser.
 
-![](../../images/web-based-access-1.png){: .with-border}
+![](../../../../../images/ucp.png){: .with-border}
 
 
 Docker UCP secures your cluster with role-based access control. From the

datacenter/ucp/2.1/guides/user/services/index.md

@@ -7,12 +7,12 @@ title: Deploy an app from the UI
 
 With Docker Universal Control Plane you can deploy applications from the UI
 using `docker-compose.yml` files. In this example, we're going to deploy an
-application that allows users to vote on whether they prefer cats or dogs.
+application that allows users to vote on whether they prefer cats or dogs. 😺 🐶
 
 ## Deploy voting application
 
-In your browser, **log in** to UCP, and navigate to the **Applications** page.
+In your browser, **log in** to UCP, and navigate to the **Stacks & Applications** page.
-There, click the **Deploy compose.yml** button, to deploy a new application.
+There, click the **Deploy** button, to deploy a new application.
 
 ![](../../images/deploy-app-ui-1.png){: .with-border}
 
@@ -25,7 +25,7 @@ The application we're going to deploy is composed of several services:
 * `db`: A PostgreSQL service which provides permanent storage on a host volume
 * `worker`: A background service that transfers votes from the queue to permanent storage
 
-Click **Services** and paste the following YAML into the **DOCKER-COMPOSE.YML**
+Click **Deploy** and paste the following YAML into the **APPLICATION DEFINITION**
 field.
 
 ```none
@@ -125,7 +125,7 @@ documentation](http://docker-docs-vnext-compose.netlify.com/compose/compose-file
 Give the application a name (such as "VotingApp," used here), and click
 **Create**.
 
-Once UCP deploys the application, click on **Services** on the left navigation,
+Once UCP deploys the application, click on **VotingApp** or go to **Services** on the left navigation,
 to see the details of the services you have deployed across your nodes. Try
 clicking on the `visualizer` service, and scroll to the bottom of the detail page.
 You'll see a link to your UCP instance's URL that includes the published port