Merge pull request #17139 from sethmanheim/acr

Fix Edge Essentials acronym

Author: prmerger-automator[bot]

AKS-Arc/aks-edge-concept-networking.md

@@ -99,7 +99,7 @@ It's possible to check the DNS servers being used for both Linux and Windows nod
     Invoke-AksEdgeNodeCommand -NodeType Linux -command "resolvectl status"
     ```
 
-    The command output shows a list of the DNS servers configured for each Linux VM interfaces. In particular, it's important to check the **eth0** interface status, which is the default interface for the AKS EE VM communication. Also, make sure to check the IP addresses of the **Current DNS Server** and **DNS Servers** fields of the list. If there's no IP address, or the IP address isn't a valid DNS server IP address, then the DNS service won't work.
+    The command output shows a list of the DNS servers configured for each Linux VM interfaces. In particular, it's important to check the **eth0** interface status, which is the default interface for the AKS Edge Essentials VM communication. Also, make sure to check the IP addresses of the **Current DNS Server** and **DNS Servers** fields of the list. If there's no IP address, or the IP address isn't a valid DNS server IP address, then the DNS service won't work.
 
 - For Windows VM nodes:
 

AKS-Arc/aks-edge-howto-multi-node-deployment.md

@@ -52,10 +52,10 @@ The key parameters to note for a scalable Kubernetes deployment are:
 > [!IMPORTANT]
 > The Kubernetes `pod cidr` is `10.42.0.0/16` for K3s and `10.244.0.0/24` for K8s. The Kubernetes `service cidr` is `10.43.0.0/16` for K3s and `10.96.0.0/12` for K8s.
 
-- `Arc`: This section is required. During the AKS Edge Essentials deployment, the Arc parameters are used to connect the AKS EE cluster to Azure Arc. For more information about the required Arc parameters, see the [connect to Arc documentation](aks-edge-howto-connect-to-arc.md).
+- `Arc`: This section is required. During the AKS Edge Essentials deployment, the Arc parameters are used to connect the AKS Edge Essentials cluster to Azure Arc. For more information about the required Arc parameters, see the [connect to Arc documentation](aks-edge-howto-connect-to-arc.md).
   
 > [!IMPORTANT]
-> Starting with the AKS Edge Essentials February 2025 release, the `Arc` section of the config file is required. The Azure Arc connection occurs automatically during AKS EE deployment.
+> Starting with the AKS Edge Essentials February 2025 release, the `Arc` section of the config file is required. The Azure Arc connection occurs automatically during AKS Edge Essentials deployment.
   
 - The `Network.NetworkPlugin` value by default is `flannel`. Flannel is the default CNI for a K3S cluster. In a K8S cluster, change the `NetworkPlugin` to `calico`.
 - In addition to the previous parameters, you can set the following parameters according to your deployment configuration, [as described here](aks-edge-deployment-config-json.md): `LinuxNode.CpuCount`, `LinuxNode.MemoryInMB`, `LinuxNode.DataSizeInGB`, `LinuxNode.Ip4Address`, `WindowsNode.CpuCount`, `WindowsNode.MemoryInMB`, `WindowsNode.Ip4Address`, `Init.ServiceIPRangeSize`, and `Network.InternetDisabled`.

AKS-Arc/aks-edge-howto-single-node-deployment.md

@@ -31,13 +31,13 @@ See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for a de
 The key parameters for single machine deployment are:
 
 - `DeploymentType`: This parameter defines the deployment type and is specified as `SingleMachineCluster`.
-- `Arc`: This section is required. During the AKS Edge Essentials deployment, the Arc parameters are used to connect the AKS EE cluster to Azure Arc. For more information about the required Arc parameters, see the [connect to Arc documentation](aks-edge-howto-connect-to-arc.md).
+- `Arc`: This section is required. During the AKS Edge Essentials deployment, the Arc parameters are used to connect the AKS Edge Essentials cluster to Azure Arc. For more information about the required Arc parameters, see the [connect to Arc documentation](aks-edge-howto-connect-to-arc.md).
 
 - The `Network.NetworkPlugin` by default is `flannel`. This is the default for a K3S cluster. If you're using a K8S cluster, change the CNI to `calico`.
 - You can set the following parameters according to your deployment configuration [as described here](aks-edge-deployment-config-json.md): `LinuxNode.CpuCount`, `LinuxNode.MemoryInMB`, `LinuxNode.DataSizeInGB`, `WindowsNode.CpuCount`, `WindowsNode.MemoryInMB`, `Init.ServiceIPRangeSize`, and `Network.InternetDisabled`.
 
 > [!IMPORTANT]
-> Starting with the AKS Edge Essentials February 2025 release, the `Arc` section of the config file is required. The Azure Arc connection occurs automatically during the AKS EE deployment.
+> Starting with the AKS Edge Essentials February 2025 release, the `Arc` section of the config file is required. The Azure Arc connection occurs automatically during the AKS Edge Essentials deployment.
 
 ## Step 2: create a single machine cluster
 

AKS-Arc/aks-edge-system-requirements.md

@@ -28,7 +28,7 @@ To better understand the etcd hardware recommendations, [see this article](https
 
 You can run AKS Edge Essentials in an Azure VM. You can create a Windows VM with either Windows 10/11 IoT Enterprise/Enterprise/Pro and Windows Server 2019, 2022 SKU, on a VM image that supports nested virtualization such as the [Dv5 and Dsv5-series](/azure/virtual-machines/dv5-dsv5-series) virtual machines. When using an Azure VM, a premium SSD is required, per the [Azure Virtual Machine documentation](/azure/virtual-machines/disks-types#disk-type-comparison). 
 
-You can also run AKS EE in a virtual machine on VMware and Hyper-V as described [here.](./aks-edge-howto-setup-nested-environment.md)
+You can also run AKS Edge Essentials in a virtual machine on VMware and Hyper-V as described [here.](./aks-edge-howto-setup-nested-environment.md)
 
 ### OS requirements
 
@@ -60,7 +60,7 @@ Install Windows 10/11 IoT Enterprise/Enterprise/Pro on your machine and activate
 - **Deployment options**: Full Kubernetes deployment on multiple machines.
 - **Workloads**: Windows worker nodes.
 - **GPU**: [GPU-PV](aks-edge-gpu.md).
-- **Secret Encryption**: [KMS plugin for AKS EE](aks-edge-howto-secret-encryption.md).
+- **Secret Encryption**: [KMS plugin for AKS Edge Essentials](aks-edge-howto-secret-encryption.md).
 - **Security**: [Workload identity](aks-edge-workload-identity.md). Workload identity federation is only available for customers deploying Azure IoT Operations on top of AKS Edge Essentials.
 - **Network plugins**: Calico on K3S (discontinued).