Merge pull request #78764 from TylerMSFT/twhitney-updateqs

Twhitney updateqs

Author: rjagiewich

articles/aks/kubernetes-walkthrough-portal.md

@@ -6,7 +6,7 @@ author: iainfoulds
 
 ms.service: container-service
 ms.topic: quickstart
-ms.date: 12/18/2018
+ms.date: 5/31/2019
 ms.author: iainfou
 ms.custom: mvc
 
@@ -29,35 +29,36 @@ Sign in to the Azure portal at https://portal.azure.com.
 
 ## Create an AKS cluster
 
-In the top left-hand corner of the Azure portal, select **+ Create a resource** > **Kubernetes Service**.
+In the top left-hand corner of the Azure portal, select **+ Create a resource** > **Containers** >  **Kubernetes Service**.
 
 To create an AKS cluster, complete the following steps:
 
-1. **Basics** - Configure the following options:
+1. On the **Basics** page, configure the following options:
    - *PROJECT DETAILS*: Select an Azure subscription, then select or create an Azure resource group, such as *myResourceGroup*. Enter a **Kubernetes cluster name**, such as *myAKSCluster*.
    - *CLUSTER DETAILS*: Select a region, Kubernetes version, and DNS name prefix for the AKS cluster.
-   - *SCALE*: Select a VM size for the AKS nodes. The VM size **cannot** be changed once an AKS cluster has been deployed.
+   - **PRIMARY NODE POOL**: select a VM size for the AKS nodes. The VM size **cannot** be changed once an AKS cluster has been deployed. 
        - Select the number of nodes to deploy into the cluster. For this quickstart, set **Node count** to *1*. Node count **can** be adjusted after the cluster has been deployed.
 
      ![Create AKS cluster - provide basic information](media/kubernetes-walkthrough-portal/create-cluster-basics.png)
 
-     Select **Next: Authentication** when complete.
+     Select **Next: Scale** when complete.
 
-1. **Authentication**: Configure the following options:
-   - Create a new service principal or *Configure* to use an existing one. When using an existing SPN, you need to provide the SPN client ID and secret.
-   - Enable the option for Kubernetes role-based access controls (RBAC). These controls provide more fine-grained control over access to the Kubernetes resources deployed in your AKS cluster.
+2. On the **Scale** page, keep the default options. At the bottom of the screen, click **Next:Authentication**.
+3. On the **Authentication** page, configure the following options:
+   - Create a new service principal by leaving the **Service Principal** field with **(new) default service principal**. Or you can choose *Configure service principal* to use an existing one. If you use an existing one, you will need to provide the SPN client ID and secret.
+   - Enable the option for Kubernetes role-based access controls (RBAC). This will provide more fine-grained control over access to the Kubernetes resources deployed in your AKS cluster.
 
-     By default, *Basic* networking is used, and Azure Monitor for containers is enabled. Select **Review + create** and then **Create** when ready.
+    By default, *Basic* networking is used, and Azure Monitor for containers is enabled. Click **Review + create** and then **Create** when validation completes.
 
-It takes a few minutes to create the AKS cluster and to be ready for use. When finished, browse to the AKS cluster resource group, such as *myResourceGroup*, and select the AKS resource, such as *myAKSCluster*. The AKS cluster dashboard is shown, as in the following example screenshot:
+It takes a few minutes to create the AKS cluster. When your deployment is complete, click **Go to resource**, or  browse to the AKS cluster resource group, such as *myResourceGroup*, and select the AKS resource, such as *myAKSCluster*. The AKS cluster dashboard is shown, as in this example:
 
 ![Example AKS dashboard in the Azure portal](media/kubernetes-walkthrough-portal/aks-portal-dashboard.png)
 
 ## Connect to the cluster
 
 To manage a Kubernetes cluster, you use [kubectl][kubectl], the Kubernetes command-line client. The `kubectl` client is pre-installed in the Azure Cloud Shell.
 
-Open Cloud Shell using the button on the top right-hand corner of the Azure portal.
+Open Cloud Shell using the `>_` button on the top of the Azure portal.
 
 ![Open the Azure Cloud Shell in the portal](media/kubernetes-walkthrough-portal/aks-cloud-shell.png)
 

articles/aks/kubernetes-walkthrough.md

@@ -236,7 +236,7 @@ To see the Azure Vote app in action, open a web browser to the external IP addre
 
 When the AKS cluster was created, Azure Monitor for containers was enabled to capture health metrics for both the cluster nodes and pods. These health metrics are available in the Azure portal.
 
-To see current status, uptime, and resource usage for the Azure Vote pods, complete the following steps:
+To see the current status, uptime, and resource usage for the Azure Vote pods, complete the following steps:
 
 1. Open a web browser to the Azure portal [https://portal.azure.com][azure-portal].
 1. Select your resource group, such as *myResourceGroup*, then select your AKS cluster, such as *myAKSCluster*.
@@ -249,11 +249,11 @@ The *azure-vote-back* and *azure-vote-front* containers are displayed, as shown
 
 ![View the health of running containers in AKS](media/kubernetes-walkthrough/monitor-containers.png)
 
-To see logs for the `azure-vote-front` pod, choose the option to **View in analytics**, then select **View container logs** link on the right-hand side of the containers list. These logs include the *stdout* and *stderr* streams from the container.
+To see logs for the `azure-vote-back` pod, choose the option to **View in analytics**, then click the **View container logs** link on the right-hand side of the containers list. These logs include the *stdout* and *stderr* streams from the container.
 
 ![View the containers logs in AKS](media/kubernetes-walkthrough/monitor-container-logs.png)
 
-## Delete cluster
+## Delete the cluster
 
 When the cluster is no longer needed, use the [az group delete][az-group-delete] command to remove the resource group, container service, and all related resources.