From ec8c9888d3ec5b14c574ea9d7affad0ca1e07790 Mon Sep 17 00:00:00 2001
From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com>
Date: Wed, 7 Nov 2018 08:14:11 -0800
Subject: [PATCH] Update upgrade.md

---
 ee/upgrade.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ee/upgrade.md b/ee/upgrade.md
index 0956d0e3d6..996a0211e8 100644
--- a/ee/upgrade.md
+++ b/ee/upgrade.md
@@ -20,7 +20,7 @@ Docker Engine - Enterprise upgrades in Swarm clusters should follow these guidel
 space exhaustion and associated application downtime.
 
 * New workloads should not be actively scheduled in the cluster during upgrades.
-* Differences in the major (X.y.z.) or minor (x.Y.z) version numbers between the managers and workers can cause mismatches between managers and workers can cause unintended consequences when new workloads are scheduled.
+* Differences in the major (X.y.z.) or minor (x.Y.z) version numbers between the managers and workers can cause unintended consequences when new workloads are scheduled.
 * Manager nodes should all be upgraded first before upgrading worker nodes. Upgrading manager nodes sequentially is recommended if live workloads are running in the cluster during the upgrade.
 * Once manager nodes are upgraded worker nodes should be upgraded next and then the Swarm cluster upgrade is complete.
 * If running UCP, the UCP upgrade should follow once all of the Swarm engines have been upgraded.