Fix title and release notes issues

Author: rcheeran

AKS-Arc/TOC.yml

@@ -13,7 +13,7 @@
     href: data-collection.md
   - name: Blogs and announcements
     href: blogs-announcements.md
-- name: AKS on Azure Local
+- name: AKS Arc on Azure Local
   expanded: true
   items:
   - name: What's new in AKS on Azure Local
@@ -332,7 +332,7 @@
       href: aks-edge-licensing.md
     - name: Microsoft Software License Terms
       href: aks-edge-software-license-terms.md 
-- name: AKS on VMware
+- name: AKS Arc on VMware
   items:
   - name: Overview
     href: aks-vmware-overview.md
@@ -380,7 +380,7 @@
         href: vmsize.yml
       - name: vnet
         href: vnet.yml
-- name: AKS on Windows Server
+- name: AKS Arc on Windows Server
   items:
   - name: AKS on Windows Server retirement
     href: aks-windows-server-retirement.md
@@ -390,7 +390,7 @@
     href: system-requirements.md
   - name: Quickstarts 
     items:
-    - name: Deploy an AKS cluster
+    - name: Deploy an AKS Arc cluster
       items:
       - name: Use PowerShell
         href: kubernetes-walkthrough-powershell.md

AKS-Arc/aks-whats-new-local.md

@@ -34,6 +34,7 @@ The following Kubernetes cluster deployment and management capabilities are avai
 
 - **Disk space exhaustion**: Fixed [issues due to disk space exhaustion on control plane VMs due to accumulation of kube-apiserver audit logs](kube-apiserver-log-overflow.md).  
 - **Cluster upgrade**: Fixed AKS Arc cluster and node pool create, scale, and [upgrade issues due to unavailability of AKS Arc VM images](gallery-image-not-usable.md).
+- **AKS Arc Telemetry pod issue**: Fixed the issue where [AKS Arc telemetry pod was consuming excessing CPU and memory](telemetry-pod-resources.md).
 - **New checks**: Added new checks during cluster and node pool operations. These improvements allow the system to proactively detect and handle scenarios where there are insufficient IP addresses in the IP pool.
 - **GPU resource allocation**: Additional pre-checks for resource allocation for GPUs during Kubernetes cluster create operation.
 - **Node pool improvements**: Accurate representation of node pool count and status on the Azure portal. This release also includes improvements to node pool creation and update flows to ensure that the Kubernetes cluster status accounts for corresponding node pool status.

AKS-Arc/aks-windows-server-retirement.md

@@ -1,6 +1,6 @@
 ---
-title: Retirement of AKS architecture on Windows Server 2019 and Windows Server 2022
-description: Learn about retirement of AKS on Windows Server 2019 and Windows Server 2022.
+title: Retirement of AKS architecture on Windows Server SKUs
+description: Learn about retirement of AKS on Windows Server SKUs - Windows Server 2019 and Windows Server 2022.
 ms.topic: how-to
 ms.custom: linux-related-content
 author: sethmanheim
@@ -37,7 +37,7 @@ The following Kubernetes cluster deployment and management capabilities are avai
 
 ## If you're using Azure Kubernetes Service on Windows Server 2019 or Windows Server 2022
 
-The AKS Arc current architecture on Windows Server 2019 and Windows Server 2022 will be retired on March 27, 2028. Starting on March 27 2028, you no longer get support, security and quality updates for your existing AKS Arc clusters. You also won't be able to deploy, upgrade or scale the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022.
+The AKS Arc current architecture on Windows Server 2019 and Windows Server 2022 will be retired on March 27, 2028. Starting on March 27 2028, you no longer get support, security and quality updates for your existing AKS Arc clusters. You also won't be able to deploy, upgrade or scale the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022. Between now and March 2028, we will not be adding support for any new Windows Server SKUs, for eg. Windows Server 2025 is not supported on AKS Arc.
 
 ## If you're using Azure Kubernetes Service on Azure Local, version 22H2
 

AKS-Arc/gallery-image-not-usable.md

@@ -47,8 +47,8 @@ This issue was fixed in [AKS on Azure Local, version 2507](/azure/azure-local/wh
 
 - Upgrade your Azure Local deployment to the 2507 build.
 - Once updated, confirm that the images were downloaded successfully by running the `az aksarc get-versions` command.
-- For new AKS clusters: new AKS clusters should now be created successfully.
-- For scaling existing AKS clusters: scaling existing AKS clusters continues to encounter issues. Please file a support case.
+- You can now use the listed Kubernetes versions while creating or updating your AKS Arc clusters.
+- If you continue to encounter issue, please file a support case.
 
 ## Next steps