Editing whole document touched.

articles/control-center/getting-started/upgrade.adoc

@@ -1,45 +1,44 @@
 ---
 title: Upgrading from 1.0 to 1.1
 page-title: Upgrading from 1.0 to 1.1
-description: Learn how to upgrade Control Center 1.0 to 1.1
-meta-description: Learn how to get upgrade Vaadin Control Center version 1.0 to 1.1.
+description: How to upgrade Control Center 1.0 to 1.1.
+meta-description: How to get upgrade Vaadin Control Center version 1.0 to 1.1.
 order: 110
 ---
 
+
 = Upgrading from 1.0 to 1.1
 
-To successfully upgrade Control Center from 1.0.X version to 1.1.X, you must perform three actions:
+To upgrade Control Center from version 1.0.x to 1.1.x, you must perform three tasks:
+
+- Add a configuration property to the Control Center configmap;
+- Create a secret that holds the email and password for the Control Center user that was created in the installation wizard; and
+- Set the Docker image of the Control Center deployment to a 1.1 version.
 
-- Add a configuration property to the Control Center configmap.
-- Create a secret that holds the email and password for the Control Center user that was created in the installation wizard.
-- Set the docker image of the Control Center deployment to a 1.1 version.
+All of the example commands below assume that Control Center was installed in the namespace called `control-center`.
 
-NOTE: All of the example commands below assume that Control Center was installed in namespace named `control-center`.
 
 == Add a New Necessary Configuration Property
 
-Control Center 1.1.0 uses a configuration property that did not exist in 1.0.
-If this property is missing, your deployment will not work after upgrading to 1.1.
-Edit the configmap for control center, adding the following under the `data` segment:
+Control Center 1.1.0 uses a configuration property that didn't exist in 1.0. If this property is missing, your deployment won't work after upgrading to 1.1. To resolve this, edit the configmap for control center, adding the following under the `data` segment:
 
 [source,yaml]
 ----
 # data:
   vaadin.control-center.keycloak.admin-secret: control-center-keycloak-initial-admin
 ----
 
-To edit the Control Center configmap, run:
+To edit the Control Center configmap, execute the following from the command-line:
 
 [source,bash]
 ----
 kubectl -n control-center edit configmap control-center
 ----
 
+
 == Create a Secret for Control Center User Credentials
 
-There must also exist a secret which holds the email and password of the main Control Center user.
-These values must be the same that were input during the installation process of the 1.0 version, in the installation wizard.
-Assuming the email was `[email protected]` and the password was `examplepassword123`, run:
+You'll need to set up a secret which holds the email and password of the main Control Center user. These values must be the same that were entered during the installation process of the 1.0 version, in the installation wizard. Assuming the email was `[email protected]` and the password was `examplepassword123`, execute the following:
 
 [source,bash]
 ----
@@ -48,14 +47,14 @@ kubectl -n control-center create secret generic control-center-user \
 --from-literal=password=examplepassword123
 ----
 
+
 == Upgrading Docker Image
 
-The last step is when you actually upgrade your deployed Control Center application to use an updated image.
-Assuming that your Control Center deployment is named `control-center`, upgrade its docker image by running:
+The last step is when you actually upgrade your deployed Control Center application to use an updated image. Assuming that your Control Center deployment is named, `control-center`, upgrade its Docker image by running this:
 
 [source,bash]
 ----
 kubectl -n control-center set image deployment/control-center app=vaadin/control-center-app:1.1.0
 ----
 
-After all these steps are completed, you should now have a working deployment of Control Center 1.1.0 in your cluster.
+After these steps are completed, you should now have a working deployment of Control Center 1.1.0 in your cluster.