From 8d55b797a0a17d055f004363388555450ee92549 Mon Sep 17 00:00:00 2001
From: Michael Iatrou <925703+iatrou@users.noreply.github.com>
Date: Fri, 8 Mar 2019 20:47:30 -0600
Subject: [PATCH] Clarify the blue/green upgrade example. (#13009)

---
 content/en/docs/getting-started-guides/ubuntu/upgrades.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/getting-started-guides/ubuntu/upgrades.md b/content/en/docs/getting-started-guides/ubuntu/upgrades.md
index b34108c2c0..5f87c0b3c8 100644
--- a/content/en/docs/getting-started-guides/ubuntu/upgrades.md
+++ b/content/en/docs/getting-started-guides/ubuntu/upgrades.md
@@ -107,15 +107,15 @@ but is a safer upgrade route.
 
 #### Blue/green worker upgrade
 
-Given a deployment where the workers are named kubernetes-alpha.
+Given a deployment where the workers are named kubernetes-blue.
 
 Deploy new workers:
 
-    juju deploy kubernetes-alpha
+    juju deploy kubernetes-green
 
 Pause the old workers so your workload migrates:
 
-    juju run-action kubernetes-alpha/# pause
+    juju run-action kubernetes-blue/# pause
 
 Verify old workloads have migrated with:
 
@@ -123,7 +123,7 @@ Verify old workloads have migrated with:
 
 Tear down old workers with:
 
-    juju remove-application kubernetes-alpha
+    juju remove-application kubernetes-blue
 
 #### In place worker upgrade