Merge branch 'screenshots-695' of github.com:docker/docs-private

ee/ucp/admin/configure/add-labels-to-cluster-nodes.md

@@ -13,12 +13,12 @@ are scheduled on a node with a specific label.
 For example, you can apply labels based on their role in the development
 lifecycle, or the hardware resources they have.
 
-![](../../images/add-labels-to-cluster-nodes-1.svg)
+![](../../images/add-labels-to-cluster-nodes-1.svg){: .with-border}
 
 Don't create labels for authorization and permissions to resources.
 Instead, use resource sets, either UCP collections or Kubernetes namespaces,
 to organize access to your cluster.
-[Learn about managing access with resource sets](../../authorization/group-resources.md).   
+[Learn about managing access with resource sets](../../authorization/group-resources.md).
 
 ## Apply labels to a node
 
@@ -26,18 +26,20 @@ In this example we'll apply the `ssd` label to a node. Then we'll deploy
 a service with a deployment constraint to make sure the service is always
 scheduled to run on a node that has the `ssd` label.
 
-Log in with administrator credentials in the UCP web UI, navigate to the
-**Nodes** page, and choose the node you want to apply labels to. In the
-details pane, click **Configure**.
+1. Log in with administrator credentials in the UCP web interface.
+2. Select **Nodes** in the left-hand navigation menu.
+3. In the nodes list, select the node to which you want to apply labels.
+4. In the details pane, select the edit node icon in the upper-right corner to edit the node.
+    ![](../../images/add-labels-to-cluster-nodes-3.png)
 
-In the **Edit Node** page, scroll down to the **Labels** section.
-
-Click **Add Label**, and add a label with the key `disk` and a value of `ssd`. 
+5. In the **Edit Node** page, scroll down to the **Labels** section.
+6. Select **Add Label**.
+7. Add a label with the key `disk` and a value of `ssd`.
 
 ![](../../images/add-labels-to-cluster-nodes-2.png){: .with-border}
 
-Click **Save** and dismiss the **Edit Node** page. In the node's details
-pane, click **Labels** to view the labels that are applied to the node. 
+8. Click **Save** then dismiss the **Edit Node** page.
+9. In the node's details pane, select **Labels** to view the labels that are applied to the node.
 
 You can also do this from the CLI by running:
 
@@ -55,10 +57,11 @@ In this example, when users deploy a service, they can add a constraint for the
 service to be scheduled only on nodes that have SSD storage:
 `node.labels.disk == ssd`.
 
-Navigate to the **Stacks** page. Name the new stack "wordpress", and in the
-**Mode** dropdown, check **Swarm Services**.
+1. Navigate to the **Stacks** page.
+2. Name the new stack "wordpress".
+3. Under **Orchestrator Mode**, select **Swarm Services**.
 
-In the **docker-compose.yml** editor, paste the following stack file.
+4. In the **docker-compose.yml** editor, paste the following stack file.
 
 ```
 version: "3.1"
@@ -103,20 +106,20 @@ networks:
   wordpress-net:
 ```
 
-Click **Create** to deploy the stack, and when the stack deploys,
+5. Click **Create** to deploy the stack, and when the stack deploys,
 click **Done**.
 
 ![](../../images/use-constraints-in-stack-deployment.png)
 
-Navigate to the **Nodes** page, and click the node that has the
+6. Navigate to the **Nodes** page, and click the node that has the
 `disk` label. In the details pane, click the **Inspect Resource**
-dropdown and select **Containers**.  
+dropdown and select **Containers**.
 
 ![](../../images/use-constraints-in-stack-deployment-2.png)
 
 Dismiss the filter and navigate to the **Nodes** page. Click a node that
 doesn't have the `disk` label. In the details pane, click the
-**Inspect Resource** dropdown and select **Containers**. There are no 
+**Inspect Resource** dropdown and select **Containers**. There are no
 WordPress containers scheduled on the node. Dismiss the filter.
 
 ## Add a constraint to a service by using the UCP web UI
@@ -125,13 +128,13 @@ You can declare the deployment constraints in your docker-compose.yml file or
 when you're creating a stack. Also, you can apply them when you're creating
 a service.
 
-To check if a service has deployment constraints, navigate to the 
+To check if a service has deployment constraints, navigate to the
 **Services** page and choose the service that you want to check.
 In the details pane, click **Constraints** to list the constraint labels.
 
 To edit the constraints on the service, click **Configure** and select
 **Details** to open the **Update Service** page. Click **Scheduling** to
-view the constraints. 
+view the constraints.
 
 ![](../../images/add-constraint-to-service.png)
 
@@ -140,5 +143,3 @@ You can add or remove deployment constraints on this page.
 ## Where to go next
 
 - [Store logs in an external system](store-logs-in-an-external-system.md)
-
-