Edit pass.

Author: LouisBerner

articles/databox-online/azure-stack-edge-gpu-2403-release-notes.md

@@ -51,31 +51,24 @@ You can update to the latest version using the following update paths:
 The 2403 release has the following new features and enhancements:
 
 - CAT-1 STIG security fixes Mariner Guest OS for AKS on Azure Stack Edge.
-- Deprecating support for AKS-Telemetry on AKS on Azure Stack Edge.
+- Deprecated support for AKS telemetry on AKS on Azure Stack Edge.
 - Zone-label support for two-node Kubernetes clusters. 
 - Hyper-V VM management: memory usage monitoring on Azure Stack Edge host.
 
 ## Issues fixed in this release
 
 | No. | Feature | Issue |
 | --- | --- | --- |
-|**1.**| Two-node cold boot of the server causes high availability VM cluster resources to come up as offline. | Changed ColdStartSetting to AlwaysStart. |
-|**2.**| Marketplace image support. | Fixed bug allowing Windows Marketplace image on Azure Stack Edge A and TMA. |
-|**3.**| Fixed VM NIC link flapping after Azure Stack Edge host power off/on, which can cause VM losing its DHCP IP. |  |
-|**4.**| Due to proxy ARP configurations in some customer environments, **IP address in use** check returns false positive even though no endpoint in the network is using the IP. | The fix skips the ARP-based VM **IP address in use** check if the IP address is allocated from an internal network managed by Azure Stack Edge. |
-|**5.**| VM NIC change operation times out after 3 hours, which blocks other VM update operations. On Microsoft Kubernetes clusters, Persistent Volume (PV) dependent pods get stuck. The issue occurs when multiple NICs within a VM are being transferred from a VLAN virtual network to a non-VLAN virtual network. The transfer involves asynchronous calls that are processed in the same thread. If one NIC transfer is made while the other NIC transfer is still processing, a deadlock could occur due to the shared API activity ID in one thread. | To mitigate this issue, the API activity ID would be uniquely generated even within one thread, ensuring that the parallel calls are independent and don't affect each other. After the fix, the VM NIC change operation times out quickly and the VM update won't be blocked. |
+|**1.**| Clustering | Two-node cold boot of the server causes high availability VM cluster resources to come up as offline. Changed ColdStartSetting to AlwaysStart. |
+|**2.**| Marketplace image support | Fixed bug allowing Windows Marketplace image on Azure Stack Edge A and TMA. |
+|**3.**| Network connectivity | Fixed VM NIC link flapping after Azure Stack Edge host power off/on, which can cause VM losing its DHCP IP. |
+|**4.**| Network connectivity |Due to proxy ARP configurations in some customer environments, **IP address in use** check returns false positive even though no endpoint in the network is using the IP. The fix skips the ARP-based VM **IP address in use** check if the IP address is allocated from an internal network managed by Azure Stack Edge. |
+|**5.**| Network connectivity | VM NIC change operation times out after 3 hours, which blocks other VM update operations. On Microsoft Kubernetes clusters, Persistent Volume (PV) dependent pods get stuck. The issue occurs when multiple NICs within a VM are being transferred from a VLAN virtual network to a non-VLAN virtual network. The transfer involves asynchronous calls that are processed in the same thread. If one NIC transfer is made while the other NIC transfer is still processing, a deadlock could occur due to the shared API activity ID in one thread. To mitigate this issue, the API activity ID would be uniquely generated even within one thread, ensuring that the parallel calls are independent and don't affect each other. After the fix, the VM NIC change operation times out quickly and the VM update won't be blocked. |
 |**6.**| Kubernetes | Overall two-node Kubernetes resiliency improvements, like increasing memory for control plane for AKS workload cluster, increasing limits for etcd, multi-replica, and hard anti-affinity support for core DNS and Azure disk csi controller pods to improve VM failover times. |
 |**7.**| Compute Diagnostic and Update | Resiliency fixes |
+|**8.**| Security | STIG security fixes. Mariner Guest OS for AKS on Azure Stack Edge. |
 
-CAT-1 STIG security fixes Mariner Guest OS for AKS on ASE. 
-
-Deprecating support for AKS-Telemetry on AKS on ASE 
-
-Zone-label support for Kubernetes cluster on two-node  
-
-Field IcM - monitor "Hyper-V Virtual Machine Management" memory usage on ASE host and keep it in check.
-
- <!--!## Known issues in this release
+<!--!## Known issues in this release
 
 | No. | Feature | Issue | Workaround/comments |
 | --- | --- | --- | --- |
@@ -86,7 +79,7 @@ Field IcM - monitor "Hyper-V Virtual Machine Management" memory usage on ASE hos
 
 | No. | Feature | Issue | Workaround/comments |
 | --- | --- | --- | --- |
-|**1.**| Azure Storage Explorer | The Blob Endpoint certificate that's autogenerated by the Azure Stack Edge device may not work properly with Azure Storage Explorer. | Replace Blob Endpoint certificate. For detailed steps, see [Bring your own certificates](azure-stack-edge-gpu-deploy-configure-certificates.md#bring-your-own-certificates). |
+|**1.**| Azure Storage Explorer | The Blob storage endpoint certificate that's autogenerated by the Azure Stack Edge device may not work properly with Azure Storage Explorer. | Replace the Blob storage endpoint certificate. For detailed steps, see [Bring your own certificates](azure-stack-edge-gpu-deploy-configure-certificates.md#bring-your-own-certificates). |
 |**2.**| Network connectivity | On a two-node Azure Stack Edge Pro 2 cluster with a teamed virtual switch for Port 1 and Port 2, if a Port 1 or Port 2 link is down, it can take up to 5 seconds to resume network connectivity on the remaining active port. If a Kubernetes cluster uses this teamed virtual switch for management traffic, pod communication may be disrupted up to 5 seconds. |  |
 |**3.**| Virtual machine | After the host or Kubernetes node pool VM is shut down, there's a chance that kubelet in node pool VM fails to start due to a CPU static policy error. Node pool VM shows **Not ready** status, and pods won't be scheduled on this VM. | Enter a support session and ssh into the node pool VM, then follow steps in [Changing the CPU Manager Policy](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#changing-the-cpu-manager-policy) to remediate the kubelet service. |