Editorial tweaks.

LouisBerner · LouisBerner · commit b103f5e87721 · 2025-02-27T10:26:08.000-08:00
diff --git a/azure-local/deploy/single-server.md b/azure-local/deploy/single-server.md
@@ -38,8 +38,10 @@ Here are the steps to install the Azure Stack HCI OS on a single server, create
     ```
 
 1. Install the Azure Stack HCI OS on your server. For more information, see [Deploy the Azure Stack HCI OS](../deploy/operating-system.md#manual-deployment) onto your server.
+
 1. Configure the server utilizing the [Server Configuration Tool](/windows-server/administration/server-core/server-core-sconfig) (SConfig).
-1. Install the required roles and features using the following command, then reboot before continuing.
+
+1. Install the required roles and features using the following command, then reboot before you continue.
 
    ```powershell
    Install-WindowsFeature -Name "BitLocker", "Data-Center-Bridging", "Failover-Clustering", "FS-FileServer", "FS-Data-Deduplication", "Hyper-V", "Hyper-V-PowerShell", "RSAT-AD-Powershell", "RSAT-Clustering-PowerShell", "NetworkATC", "Storage-Replica", -IncludeAllSubFeature -IncludeManagementTools
@@ -64,6 +66,7 @@ Here are the steps to install the Azure Stack HCI OS on a single server, create
    > - The `New-Cluster` command requires the `StaticAddress` parameter if the node isn't using DHCP for its IP address assignment. This parameter should be supplied with a new, available IP address on the node's subnet.
 
 1. Use [PowerShell](../deploy/register-with-azure.md?tab=power-shell#register-a-cluster) or [Windows Admin Center](../deploy/register-with-azure.md?tab=windows-admin-center#register-a-cluster) to register the cluster.
+
 1. [Create volumes](/windows-server/storage/storage-spaces/create-volumes).
 
 ## Updating single-node clusters
@@ -76,16 +79,20 @@ For solution updates (such as driver and firmware updates), see your solution ve
 
 ## Change a single-node to a multi-node cluster (optional)
 
-You can add servers to your single-node cluster, also known as scaling out, though there are some manual steps you must take to properly configure Storage Spaces Direct fault domains (`FaultDomainAwarenessDefault`) in the process. These steps aren't present when adding servers to clusters with two or more servers.
+You can add servers to your single-node cluster, also known as scaling out, though there are some manual steps you must take to properly configure Storage Spaces Direct fault domains (`FaultDomainAwarenessDefault`) in the process. These steps aren't present when you add servers to clusters with two or more servers.
 
 1. Validate the cluster by specifying the existing server and the new server: [Validate an Azure Stack HCI cluster - Azure Stack HCI | Microsoft Docs](../deploy/validate.md).
+
 2. If cluster validation was successful, add the new server to the cluster: [Add or remove servers for an Azure Stack HCI cluster - Azure Stack HCI | Microsoft Docs](../manage/add-cluster.md).
+
 3. Once the server is added, change the cluster's fault domain awareness from PhysicalDisk to ScaleScaleUnit: [Inline fault domain changes](../manage/single-node-scale-out.md#inline-fault-domain-changes).
+
 4. Optionally, if more resiliency is needed, adjust the volume resiliency type from a 2-way mirror to a Nested 2-way mirror: [Single-server to two-node cluster](../manage/single-node-scale-out.md#single-server-to-two-node-cluster).
+
 5. [Set up a cluster witness](../manage/witness.md).
 
 ## Next steps
 
-- [Deploy workload – AVD](../deploy/virtual-desktop-infrastructure.md)
-- [Deploy workload – AKS-HCI](/azure-stack/aks-hci/overview)
-- [Deploy workload – Azure Arc-enabled data services](/azure/azure-arc/data/overview)
+- [Deploy workload – AVD](../deploy/virtual-desktop-infrastructure.md).
+- [Deploy workload – AKS-HCI](/azure-stack/aks-hci/overview).
+- [Deploy workload – Azure Arc-enabled data services](/azure/azure-arc/data/overview).
diff --git a/azure-stack/user/aks-how-to-use-cli.md b/azure-stack/user/aks-how-to-use-cli.md
@@ -18,17 +18,17 @@ ms.lastreviewed: 10/06/2022
 
 This article is a guide to get you started using the Azure Kubernetes Service (AKS) service on Azure Stack Hub. It describes the main set of scenarios to get you familiarized with AKS on Azure Stack Hub. The functionality available in Azure Stack Hub is a [subset](aks-overview.md) of what is available in global Azure.
 
-In the following sections you will:
+In the following sections you:
 
 1. Complete the prerequisites to use AKS on Azure Stack Hub.
 
 2. Complete the lifecycle operations of an AKS cluster using Azure CLI and the Azure Stack Hub user portal.
 
 ### Install Azure CLI
 
-You'll need to install the Azure CLI with AKS support for your machine. Prepare a clean machine Linux or Windows machine to install the preview version of the Azure CLI with AKS support. Ensure the machine doesn't have Azure CLI installed to avoid conflicting with preview of Azure CLI you'll install next. Most of the following instructions assume you're using a Linux VM, but you can find the equivalent steps in Windows in the product documentation.
+You must install the Azure CLI with AKS support for your machine. Prepare a clean machine Linux or Windows machine to install the preview version of the Azure CLI with AKS support. Ensure the machine doesn't have Azure CLI installed to avoid conflicting with preview of Azure CLI you install next. Most of the following instructions assume you're using a Linux VM, but you can find the equivalent steps in Windows in the product documentation.
 
-Don't upgrade Azure CLI after installing the Azure CLI with AKS support. If you do upgrade, it is replaced by the production ready version that lacks AKS support.
+Don't upgrade Azure CLI after installing the Azure CLI with AKS support. If you do upgrade, it's replaced by the production ready version that lacks AKS support.
 
 ### [Ubuntu](#tab/ubuntu)
 
@@ -80,7 +80,7 @@ Azure CLI should be 2.28.0 or later.
 ---
 ### Connect to Azure Stack Hub
 
-1. Connect to your Azure Stack Hub endpoint. You need to use Azure CLI to establish the specific Azure Stack Hub environment to which you're connecting. You can find the instructions at [Connect to Azure Stack Hub](/azure-stack/user/azure-stack-version-profiles-azurecli2?tabs=ad-win#connect-with-azure-cli)
+1. Connect to your Azure Stack Hub endpoint. You need to use Azure CLI to establish the specific Azure Stack Hub environment to which you're connecting. You can find the instructions at [Connect to Azure Stack Hub](/azure-stack/user/azure-stack-version-profiles-azurecli2?tabs=ad-win#connect-with-azure-cli).
 
 2. Register your environment so that Azure CLI can connect to the Azure Stack Hub Resource Manager endpoint for your instance. Update the URLs in the following snippet and run the following command:
 
@@ -115,7 +115,7 @@ Azure CLI should be 2.28.0 or later.
     > 
     > In particular, for Linux machines see: [Microsoft Entra ID on Linux](azure-stack-version-profiles-azurecli2.md)
 
-6. Set the subscription in your Azure CLI session as the default with:
+6. Use the following command to set the subscription in your Azure CLI session as the default:
 
     ```azurecli  
     az account set --subscription <subscription-id>
@@ -139,7 +139,7 @@ Azure CLI should be 2.28.0 or later.
 
 9. Rerun step 7 to verify the resource provider registration status. The registration can take several minutes to complete.
 
-Once those prerequisite steps are completed, you can proceed to test the following scenarios.
+Once those prerequisite steps are completed, you can test the following scenarios.
 
 ## Create an AKS cluster
 
@@ -190,7 +190,7 @@ You can find the global Azure instructions at [Deploy an Azure Kubernetes Servic
         az group create --name myResourceGroup-Win --location <your stamp location>
     ```
 
-2. Create an Azure Kubernetes az login
+2. Create an Azure Kubernetes az login.
 
 3. Service cluster.
 
@@ -215,7 +215,7 @@ You can find the global Azure instructions at [Deploy an Azure Kubernetes Servic
     --kubernetes-version 1.20.7
     ```
 
-4. Now you can proceed to repeat the tests for [Scale](#scale-cluster), [deploy a Windows app](aks-how-to-push-an-app-cli.md), and [Delete](#delete-cluster).
+4. Now you can repeat the tests for [Scale](#scale-cluster), [deploy a Windows app](aks-how-to-push-an-app-cli.md), and [Delete](#delete-cluster).
 
 ---
 
@@ -239,7 +239,7 @@ You can find the global Azure instructions at [Deploy an Azure Kubernetes Servic
     kubectl get nodes
     ```
 
-![verify the connection to your cluster](media/aks-how-to-use/verify-the-connection-to-your-cluster.png)
+   ![verify the connection to your cluster](media/aks-how-to-use/verify-the-connection-to-your-cluster.png)
 
 ## Scale cluster
 
@@ -290,7 +290,11 @@ az aks delete --name myakscluster --resource-group myResourceGroup
 
 ## Create AKS cluster with custom virtual network
 
-Creating a cluster to be deployed in a user-provided network is a common scenario. Planning the network configuration takes some preparation. Also, notice that with AKS the default network plugin is Azure CNI, not Kubenet as is the case with AKS engine. With Azure CNI, every pod gets an IP address from the subnet and can be accessed directly (without the need for a Routing table as is the case with Kubenet). These IP addresses must be unique across your network space and must be planned. The following article walks you through the process of planning for your custom virtual network deployment. You can find various network configurations that work for your needs and test them. For an initial test, the following two steps show you the basic process:
+Creating a cluster to be deployed in a user-provided network is a common scenario. Planning the network configuration takes some preparation. Also, notice that with AKS the default network plugin is Azure CNI, not Kubenet as is the case with AKS engine. 
+
+With Azure CNI, every pod gets an IP address from the subnet and can be accessed directly (without the need for a Routing table as is the case with Kubenet). These IP addresses must be unique across your network space and must be planned.
+
+The following article walks you through the process of planning for your custom virtual network deployment. You can find various network configurations that work for your needs and test them. For an initial test, the following two steps show you the basic process:
 
 1. Follow the instructions in [this article](/azure/aks/configure-azure-cni) to plan the deployment using Azure CNI. For example, you could use the portal to create a virtual network named "myAKSVnet" with IP range 10.0.0.0/8 with subnet "myAKSSubnet" and IP range 10.240.0.0/16 in a Resource Group named "myTest-rg." Then use the next step for the creation of the cluster.
 
