Further edits

Author: gitName

learn-pr/azure/aks-optimize-compute-costs/includes/3-exercise-node-pools.md

@@ -1,8 +1,8 @@
 Azure Kubernetes Service allows you to create different node pools to match specific workloads to the nodes running in each node pool.
 
-Recall from the drone-tracking example that your team developed a new predictive-modeling service that processes flight-path information in extreme weather conditions and creates optimal flight routes. This service requires GPU-based virtual-machine (VM) support and runs only on specific days during the week. The team wants to make sure no VMS are used when the service doesn't run.
+Recall from the drone-tracking example that your team developed a new predictive modeling service that processes flight-path information in extreme weather conditions and creates optimal flight routes. This service requires GPU-based virtual-machine (VM) support and runs only on specific days during the week. The team wants to make sure no VMS are used when the service doesn't run.
 
-Here, you'll create an Azure Kubernetes Service (AKS)-managed Kubernetes cluster. Next, you'll configure the cluster to support multiple node pools and allows clusters to scale the nodes in the node pools. Then, you'll add a second node pool to support user workloads with a dynamic node count. Finally, you'll scale the node count to zero to reduce the cost of the nodes used in your AKS cluster.
+Here, you'll create an Azure Kubernetes Service (AKS)-managed Kubernetes cluster. Next, you'll configure the cluster to support multiple node pools and allow clusters to scale the nodes in the node pools. Then, you'll add a second node pool to support user workloads with a dynamic node count. Finally, you'll scale the node count to zero to reduce the cost of the nodes used in your AKS cluster.
 
 ## Create a new resource group
 
@@ -13,6 +13,8 @@ Here, you'll create an Azure Kubernetes Service (AKS)-managed Kubernetes cluster
 
 1. You'll reuse the values you create here throughout all the exercises in this module. Save the output for future use.
 
+1. At the top of the Cloud Shell window, select **Settings** > **Go to Classic version**.
+
 1. Choose a region to host your resource group. Features from later exercises aren't available in all regions. For this reason, we recommend that you use **eastus** as your region. If you choose to use a different value, change the value of `REGION_NAME`.
 
     Run the following commands to register your variables:
@@ -50,7 +52,7 @@ With the resource group created, you can create AKS clusters within the group. Y
     ```azurecli
     VERSION=$(az aks get-versions \
         --location $REGION_NAME \
-        --query "values[?isPreview==null].version | [-1]" \
+        --query "values[?isPreview==null].version | [1]" \
         --output tsv)
     echo $VERSION
     ```

learn-pr/azure/aks-optimize-compute-costs/includes/4-spot-node-pools.md

@@ -2,7 +2,7 @@ Azure provides Azure Virtual Machine instances that offer scalability while redu
 
 Your company's drone-tracking solution is deployed on Azure Kubernetes Service (AKS) as many containerized applications and services. One of these services is a batch-processing service that schedules drone flight paths. With a sudden growth in your customer base, the batch-processing service gets inundated with requests and builds up a backlog of deliveries. This situation is causing delays and customer frustration.
 
-Automatically scaling the number of batch-processing service replicas provides for timely order processing. However, it also requires you to deploy more nodes to keep up with computing resource needs. Analyzing usage trends in Azure Monitor, you notice that these nodes are used only at specific times and not in a cost-effective way. The batch-processing service is stateless and doesn't save any client-session data. You realize that you can save money by:
+Automatically scaling the number of batch-processing service replicas provides for timely order processing. However, it also requires you to deploy more nodes to keep up with computing resource needs. Analyzing usage trends in Azure Monitor, you notice that these nodes are used only at specific times, and not in a cost-effective way. The batch-processing service is stateless and doesn't save any client-session data. You realize that you can save money by:
 
 - Using lower-cost node instances.
 - Automatically scaling the node count in the node pool that's configured for batch processing.
@@ -33,7 +33,7 @@ A spot virtual machine scale set is a virtual machine scale set that supports Az
 
 - **Deallocate**: The Deallocate policy functions exactly as described earlier.
 
-- **Delete**:  The Delete policy allows you to avoid the cost of disks and hitting quota limits. With the Delete eviction policy, evicted VMs are deleted together with their underlying disks. The scale set's autoscaling feature can now automatically try to compensate for VM eviction by creating new VMs. Although the creation of VMs isn't guaranteed, the evicted VMs don't count toward your vCPU quota or incur costs for underlying disks.  
+- **Delete**: The Delete policy allows you to avoid the cost of disks and hitting quota limits. With the Delete eviction policy, evicted VMs are deleted together with their underlying disks. The scale set's autoscaling feature can now automatically try to compensate for VM eviction by creating new VMs. Although the creation of VMs isn't guaranteed, the evicted VMs don't count toward your vCPU quota or incur costs for underlying disks.  
 
     A best practice is to use the autoscale feature only when you set the eviction policy to **Delete** on the scale set.
 
@@ -60,7 +60,7 @@ As the demand for nodes increases, the cluster autoscaler can scale the number o
 Before you decide to add a spot user node pool to your AKS cluster, consider the following limitations:
 
 - The underlying spot scale set is deployed only to a single fault domain and offers no high-availability guarantees.
-- The AKS cluster needs multiple node-pool support to be enabled.
+- The AKS cluster needs multiple-node-pool support to be enabled.
 - You can use spot node pools only as user node pools.
 - You can't upgrade spot node pools.
 - The creation of spot VMs isn't guaranteed. The creation of spot nodes depends on capacity and quota availability in the cluster's deployed Azure region.
@@ -78,7 +78,7 @@ You set several parameters for a new node pool to configure it as a spot node po
 
 ### Priority
 
-The `--priority` parameter is set to `Regular` by default for a new node pool. Set the value to `Spot` to indicate that the new pool you're creating is a spot node pool. This value can't be changed after creation.
+The `--priority` parameter is set to `Regular` by default for a new node pool. Set the value to `Spot` to indicate that the new pool you're creating is a spot node pool. You can't change this value after creation.
 
 ### Eviction policy
 
@@ -93,7 +93,7 @@ Spot node pools optimize costs by capping the maximum amount that you're willing
 You can set this value to any positive amount up to five decimal places, or set it to `-1`. Setting the `--spot-max-price` value to `-1` affects your node pool in the following ways:
 
 - Nodes aren't be evicted based on the node's price.
-- The cost for new nodes is based on the current price for spot nodes, or the price for a standard node, using whichever is lower.
+- The cost for new nodes is based on the current price for spot nodes or the price for a standard node; whichever is lower.
 
 For example, if you set the value to 0.98765, the maximum price for a node in USD is 0.98765 per hour. When the node's consumption exceeds this amount, it's evicted.
 

learn-pr/azure/aks-optimize-compute-costs/includes/6-resource-quota-azure-policy.md

@@ -1,4 +1,4 @@
-Azure Policy helps you to enforce standards and assess compliance at scale for your cloud environment. It's good practice for companies to implement business rules to define how employees are allowed to use company software, hardware, and other resources in the organization. Therefore, businesses use policies to enforce, review, and define access. A policy helps an organization meet governance and legal requirements, implement best practices, and establish organizational conventions.
+Azure Policy helps you enforce standards and assess compliance at scale for your cloud environment. It's good practice for companies to implement business rules to define how employees are allowed to use company software, hardware, and other resources in the organization. Therefore, businesses use policies to enforce, review, and define access. A policy helps an organization meet governance and legal requirements, implement best practices, and establish organizational conventions.
 
 Azure Kubernetes Service (AKS) allows you to orchestrate your cloud-native applications efficiently with policies. You realize that you need to enforce business rules to manage how the teams use AKS to ensure a cost-effective approach. You decide to use Azure Policy to apply this idea on your Azure-based cloud resources.
 
@@ -22,9 +22,9 @@ The *Open Policy Agent (OPA)* is an open-source, general-purpose policy engine t
 
 ## What is the OPA Gatekeeper?
 
-The *OPA Gatekeeper* is an open-source, validating, Kubernetes admission-controller webhook that enforces Custom Resource Definition (CRD)-based policies that follow the OPA syntax.
+The *OPA Gatekeeper* is an open-source, validating, Kubernetes admission controller webhook that enforces Custom Resource Definition (CRD)-based policies that follow the OPA syntax.
 
-The goal of the OPA Gatekeeper is to allow you to customize admission policies by using configuration instead of hard-coded policy rules for services. It also gives you a full view of your cluster to identify policy-violating resources.
+The OPA Gatekeeper's goal is to allow you to customize admission policies by using configuration instead of hard-coded policy rules for services. It also gives you a full view of your cluster to identify policy-violating resources.
 
 Use the OPA Gatekeeper to define organization-wide policies with rules:
 
@@ -80,7 +80,7 @@ There are a few steps to registering the Azure Policy Add-on for AKS feature. We
         --resource-group myResourceGroup
     ```
 
-    Activating the addon schedules workloads in two namespaces on your cluster. The first namespace is **kube-system**, which contains the `azure-policy` and `azure-policy-webhook`. The second namespace is **gatekeeper-system**, which contains the `gatekeeper-controller-manager`. These workloads are responsible for evaluating requests submitted to the AKS control plane. Based on your configured policies, your policy webhook can allow or deny requests.
+    Activating the add-on schedules workloads in two namespaces on your cluster. The first namespace is **kube-system**, which contains the `azure-policy` and `azure-policy-webhook`. The second namespace is **gatekeeper-system**, which contains the `gatekeeper-controller-manager`. These workloads are responsible for evaluating requests submitted to the AKS control plane. Based on your configured policies, your policy webhook can allow or deny requests.
 
 ## Assign a built-in policy definition
 
@@ -154,7 +154,7 @@ For example, for the resource-management policy, you can select **audit**, **den
 
 This table lists all the effects currently supported in policy definitions:
 
-| Effect | Description |
+| Effect | Description ||
 | --- | --- |
 | **Append** | Adds more fields to the requested resource |
 | **Audit** | Creates a warning event in the activity log |

learn-pr/azure/aks-optimize-compute-costs/includes/7-exercise-resource-quota-azure-policy.md

@@ -37,7 +37,7 @@ In this exercise, you'll enable Azure Policy for AKS on your cluster and add the
     az feature register --namespace Microsoft.ContainerService --name AKS-AzurePolicyAutoApprove
     ```
 
-1. Check that the registration was successful by querying the feature-list table. Use the `az feature list` command to run the query. The feature's registration can take several minutes to finish, so you have to check the result periodically.
+1. Check that the registration succeeded by querying the feature-list table. Use the `az feature list` command to run the query. The feature's registration can take several minutes to finish, so you have to check the result periodically.
 
     ```azurecli
     az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/AKS-AzurePolicyAutoApprove')].   {Name:name,State:properties.state}"
@@ -143,10 +143,10 @@ To configure the new Azure Policy, use the Policy service in the Azure portal.
     | Exclusions | Leave empty. |
     | **Basics** |
     | Policy definition | Select the ellipsis button. The **Available Definitions** pane appears. In the **Search** box, filter the selection by entering *CPU*. On the **Policy Definitions** tab, select the **Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits**, then select **Add**. |
+    | Version | Accept default. |
     | Assignment name | Accept default. |
     | Description | Leave empty. |
     | Policy enforcement | Make sure this option is set to **Enabled**. |
-    | Assigned by | Accept default. |
 
     Here's an example of the completed **Basics** tab:
 
@@ -161,7 +161,7 @@ To configure the new Azure Policy, use the Policy service in the Azure portal.
     | Max allowed CPU units | Set the value to **200m**. The policy matches this value to both the workload resource-request value and the workload limit value specified in the workload's manifest file. |
     | Max allowed memory bytes | Set the value to **256Mi**. The policy matches this value to both the workload resource-request value and the workload limit value specified in the workload's manifest file. |
 
-    Here's an example of the completed **Parameters** tab:
+    Leave all other values as default. Here's an example of the completed **Parameters** tab:
 
     :::image type="content" source="../media/7-complete-parameters-tab.png" alt-text="Screenshot that shows the information captured in the Parameters tab.":::
 
@@ -182,6 +182,8 @@ The final step is to test the new policy. Deploy your test workload with resourc
 
 1. Open Azure Cloud Shell and be sure to select the Bash version of Cloud Shell.
 
+1. At the top of the Cloud Shell window, select **Settings** > **Go to Classic version**.
+
 1. Create a manifest file for the Kubernetes deployment by using the integrated editor. Call the file `test-policy.yaml`:
 
     ```bash

learn-pr/azure/aks-optimize-compute-costs/includes/8-summary.md

@@ -39,7 +39,7 @@ In this module, you created billed resources on your Azure subscription. The fol
 
 ## Optional: Clean up services
 
-In this module, you also registered service providers within Azure to access their features. There's no extra charge for registering the providers or features. Follow these steps to unregister.
+In this module, you also registered service providers within Azure to access their features. There's no extra charge for registering the providers or features. Follow these steps to unregister the policies and providers.
 
 1. Run the following command to unregister the Azure Policy on AKS feature.
 
@@ -55,7 +55,7 @@ In this module, you also registered service providers within Azure to access the
     ```
 
     > [!IMPORTANT]
-    > If you choose to unregister, then the optimization features covered in the learning module aren't able until you register.
+    > If you choose to unregister, then the optimization features covered in the learning module aren't available again until you register.
 
 ## Learn more