Line edits

Author: lootle1

learn-pr/azure/aks-deploy-container-app/includes/1-introduction.md

@@ -16,7 +16,7 @@ By the end of this module, you can:
 - Familiarity with Kubernetes concepts. If you're new to Kubernetes, start with the [basics of Kubernetes](https://azure.microsoft.com/topic/what-is-kubernetes/?azure-portal=true).
 - Familiarity with [Git](/contribute/git-github-fundamentals) and [GitHub](https://github.com).
 - Familiarity with [Docker](https://docker.com) and Docker images.
-- An active Azure [subscription](https://azure.microsoft.com/free/services/kubernetes-service/?azure-portal=true).
+- An active Azure [subscription](https://azure.microsoft.com/pricing/purchase-options/azure-account).
 - Ability to use the [Azure CLI](/azure/aks/kubernetes-walkthrough).
 - Ability to create a Docker container. If you're new to Docker, start with the [intro to containers](/training/modules/intro-to-containers/).
 

learn-pr/azure/aks-deploy-container-app/includes/2-create-aks-cluster.md

@@ -26,7 +26,7 @@ There are two popular cluster architectures for Kubernetes-based deployments.
 
 :::image type="content" source="../media/2-1-diagram.png" alt-text="A diagram that shows a single control plane and multiple nodes in a cluster configuration.":::
 
-The *single control plane to multiple nodes* per cluster architecture is the most common architectural pattern, and is the easiest to deploy, but it doesn't provide high availability to your cluster's core management services.
+The *single control plane to multiple nodes* per cluster architecture is the most common architectural pattern and is the easiest to deploy, but it doesn't provide high availability to your cluster's core management services.
 
 If the control plane node becomes unavailable for any reason, no other interaction can happen with the cluster. This problem occurs even if you're the operator, or by any workloads that use Kubernetes' APIs to communicate until, at least, the API server is back online.
 
@@ -68,4 +68,4 @@ You can change the node count later in the cluster's configuration panel. It's a
 
 ## Node VM size
 
-Select from a wide range of VM specs. For development purposes, you can choose the B series to save on costs. In the exercises, you use series B2, the standard size. For more guidance to select a VM based on your needs, visit the [Azure VM selector tool](https://azure.microsoft.com/pricing/vm-selector/)
+Select from a wide range of VM specs. For development purposes, you can choose the B series to save on costs. In the exercises, you use series B2, the standard size. For more guidance to select a VM based on your needs, [ask Microsoft Copilot in Azure to find the best VM](https://techcommunity.microsoft.com/blog/azurecompute/using-microsoft-copilot-in-azure-to-find-the-best-vm-size-for-you/4356049)

learn-pr/azure/aks-deploy-container-app/includes/3-exercise-create-aks-cluster.md

@@ -1,6 +1,6 @@
 In this exercise, create an AKS cluster that uses several nodes to meet the demand of many customers using the service. You decide to use the *single control plane and multiple nodes* architecture because it provides the best way to create and manage workload resources.
 
-AKS supports both Linux and Windows node pools via the Portal or Azure CLI, however, if you're going to use Windows node pools, the cluster must be created with extra **prerequisites** and commands. Select an OS based on which type of node pools you want to add.
+AKS supports both Linux and Windows node pools via the Portal or Azure CLI. However, if you're going to use Windows node pools, the cluster must be created with extra **prerequisites** and commands. Select an OS based on which type of node pools you want to add.
 
 [!INCLUDE [azure-exercise-subscription-prerequisite](../../../includes/azure-exercise-subscription-prerequisite.md)]
 
@@ -14,7 +14,7 @@ AKS supports both Linux and Windows node pools via the Portal or Azure CLI, howe
     > [!IMPORTANT]
     > We'll run all the scripts with Bash, so if you haven't created a Cloud Shell yet, select *Bash* as the running shell.
 
-1. In the Cloud Shell window, select the **More** icon (**...**), then select **Settings** > **Go to Classic version**.
+1. In the Cloud Shell window, select **Settings** > **Go to Classic version**.
 
 1. Create variables for the configuration values you reuse throughout the exercises.