Final tweaks

Author: sethmanheim

AKS-Arc/configure-custom-load-balancer.md

@@ -49,7 +49,7 @@ This configuration assumes you want to use a custom load balancer in your cluste
 
 1. Manually configure your load balancer.  
 
-If you run an upgrade, the load balancer configuration (`loadBalancerSku` and `count`) you defined during installation remains the same after the upgrade completes. However, if you want to update `loadBalancerSku` during an upgrade, you must redeploy your workload clusters. If you have existing clusters running a HAProxy-based load balancer, you can continue running your workloads and the upgrade completes successfully.
+If you run an upgrade, the load balancer configuration (`loadBalancerSku` and `count`) you defined during installation remains the same after the upgrade completes. However, if you want to update `loadBalancerSku` during an upgrade, you must redeploy your workload clusters. If you have existing clusters running a HAProxy-based load balancer, you can continue running your workloads. The upgrade then completes successfully.
 
 > [!IMPORTANT]
 > If you change from using a custom load balancer to using the default load balancer, you're required to redeploy your workload cluster with the new load balancer configuration. For information about how to configure the default load balancer, see [Configure load balancer](configure-load-balancer.md).  

AKS-Arc/kubernetes-walkthrough-powershell.md

@@ -224,9 +224,9 @@ Set-AksHciNodePool -clusterName mycluster -name linuxnodepool -count 3
 ```
 
 > [!NOTE]
-> In previous versions of AKS on Windows Server, the [Set-AksHciCluster](/azure-stack/aks-hci/reference/ps/set-akshcicluster) command was also used to scale worker nodes. Now that AKS is introducing node pools in workload clusters, you can only use this command to scale worker nodes if your cluster was created with the old parameter set in [New-AksHciCluster](/azure-stack/aks-hci/reference/ps/new-akshcicluster).
+> In previous versions of AKS on Windows Server, the [Set-AksHciCluster](/azure/azure-local/reference/ps/set-akshcicluster) command was also used to scale worker nodes. Now that AKS is introducing node pools in workload clusters, you can only use this command to scale worker nodes if your cluster was created with the old parameter set in [New-AksHciCluster](/azure/azure-local/reference/ps/new-akshcicluster).
 
-To scale worker nodes in a node pool, use the [Set-AksHciNodePool](/azure-stack/aks-hci/reference/ps/set-akshcinodepool) command.
+To scale worker nodes in a node pool, use the [Set-AksHciNodePool](/azure/azure-local/reference/ps/set-akshcinodepool) command.
 
 ## Access your clusters using kubectl
 

AKS-Arc/restrict-ssh-access-22h2.md

@@ -1,6 +1,6 @@
 ---
 title: Restrict SSH access to virtual machines in AKS on Windows Server
-description: Learn how to restrict SSH access in AKS Arc on Windows Server.
+description: Learn how to restrict SSH access in AKS on Windows Server.
 author: sethmanheim
 ms.topic: how-to
 ms.date: 04/02/2025

AKS-Arc/system-requirements.md

@@ -57,7 +57,7 @@ This minimum requirement is for an AKS deployment with one worker node for runni
 
 For a production environment, final sizing depends on the application and number of worker nodes you're planning to deploy on the Windows Server cluster. If you choose to run AKS on a single-node Windows Server, you don't get features like high availability that come with running AKS on a Windows Server failover cluster.
 
-You must install the same operating system on each server in the cluster. If you're using Windows Server Datacenter, the same OS and version must be the same on each server in the cluster. Each OS must use the **en-us** region and language selections. You can't change these settings after installation.
+You must install the same operating system on each server in the cluster. In Windows Server Datacenter, the same OS and version must be the same on each server in the cluster. Each OS must use the **en-us** region and language selections. You can't change these settings after installation.
 
 ## Storage requirements
 

AKS-Arc/troubleshoot-overview.md

@@ -39,7 +39,7 @@ AKS on Windows Server troubleshooting topics are organized by functional area. U
 - [General](/azure-stack/aks-hci/known-issues)
 
 > [!NOTE]
-> If none of the workarounds found in the links above apply to you, [open a support issue](help-support.md).
+> If none of the workarounds found in these links apply to you, [open a support issue](help-support.md).
 
 ## Next steps