From 4ff71f3218d86c5c345b6354c93ce34516f67c89 Mon Sep 17 00:00:00 2001
From: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
Date: Mon, 18 Jan 2021 14:56:02 +0000
Subject: [PATCH] Minor style updates

---
 cloud/ecs-integration.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/cloud/ecs-integration.md b/cloud/ecs-integration.md
index 1bb9f320cf..a0c3320b05 100644
--- a/cloud/ecs-integration.md
+++ b/cloud/ecs-integration.md
@@ -196,8 +196,10 @@ The Docker Compose CLI automatically configures authorization so you can pull pr
 
 For your convenience, the Docker Compose CLI offers the `docker secret` command, so you can manage secrets created on AWS SMS without having to install the AWS CLI.
 
-First, create `token.json` file to define your DockerHub username and access token. 
-See [this document](https://docs.docker.com/docker-hub/access-tokens/) on generating managing access tokens:
+First, create a `token.json` file to define your DockerHub username and access token.
+
+For instructions on how to generate access tokens, see [Managing access tokens](https://docs.docker.com/docker-hub/access-tokens/).
+
 ```json
 {
   "username":"DockerHubUserName",
@@ -205,7 +207,7 @@ See [this document](https://docs.docker.com/docker-hub/access-tokens/) on genera
 }
 ```
 
-The you can create a secret from this file using `docker secret`:
+You can then create a secret from this file using `docker secret`:
 
 ```console
 docker secret create dockerhubAccessToken token.json