From d81ffd0a2f4b0b6d76d237ea0e7234afd2ec37f7 Mon Sep 17 00:00:00 2001
From: L-Hudson <44844738+L-Hudson@users.noreply.github.com>
Date: Fri, 7 Dec 2018 08:18:11 -0500
Subject: [PATCH] Update certify-images.md

edit ^article
---
 docker-hub/publish/certify-images.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker-hub/publish/certify-images.md b/docker-hub/publish/certify-images.md
index a391304aed..ab96a2045a 100644
--- a/docker-hub/publish/certify-images.md
+++ b/docker-hub/publish/certify-images.md
@@ -46,7 +46,7 @@ The `inspectDockerImage` tool will detect issues and output them as **warnings**
 
 If you are publishing and certifying multiple versions for a Docker image, you will need to run the `inspectDockerImage` tool on each Docker image and send each result to Docker Hub.
 
-If you are publishing and certifying multi-architecture Docker image (for example, Linux, Power, s390x, Windows) you will need to run the `inspectDockerImage` tool on the Docker EE server running on each architecture and send the results to Docker Hub.
+If you are publishing and certifying a multi-architecture Docker image (for example, Linux, Power, s390x, Windows) you will need to run the `inspectDockerImage` tool on the Docker EE server running on each architecture and send the results to Docker Hub.
 
 Details on how to run the `inspectDockerImage` tool and send the results to Docker Hub are in the sections that follow.