Updated artwork and 2403 version numbers.

Author: LouisBerner

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

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: article
-ms.date: 04/01/2024
+ms.date: 04/02/2024
 ms.author: alkohli
 ---
 
@@ -117,7 +117,7 @@ The following table provides a summary of known issues carried over from the pre
 |**26.**|Azure IoT Edge |The managed Azure IoT Edge solution on Azure Stack Edge is running on an older, obsolete IoT Edge runtime that is at end of life. For more information, see [IoT Edge v1.1 EoL: What does that mean for me?](https://techcommunity.microsoft.com/t5/internet-of-things-blog/iot-edge-v1-1-eol-what-does-that-mean-for-me/ba-p/3662137). Although the solution doesn't stop working past end of life, there are no plans to update it.  |To run the latest version of Azure IoT Edge [LTSs](../iot-edge/version-history.md#version-history) with the latest updates and features on their Azure Stack Edge, we **recommend** that you deploy a [customer self-managed IoT Edge solution](azure-stack-edge-gpu-deploy-iot-edge-linux-vm.md) that runs on a Linux VM. For more information, see [Move workloads from managed IoT Edge on Azure Stack Edge to an IoT Edge solution on a Linux VM](azure-stack-edge-move-to-self-service-iot-edge.md). |
 |**27.**|AKS on Azure Stack Edge |In this release, you can't modify the virtual networks once the AKS cluster is deployed on your Azure Stack Edge cluster.| To modify the virtual network, you'll need to delete the AKS cluster, then modify virtual networks, and then recreate AKS cluster on your Azure Stack Edge. |
 |**28.**|AKS Update |The AKS Kubernetes update might fail if one of the AKS VMs isn't running. This issue might be seen in the two-node cluster. |If the AKS update has failed, [Connect to the PowerShell interface of the device](azure-stack-edge-gpu-connect-powershell-interface.md). Check the state of the Kubernetes VMs by running `Get-VM` cmdlet. If the VM is off, run the `Start-VM` cmdlet to restart the VM. Once the Kubernetes VM is running, reapply the update. |
-|**29.**|Wi-Fi |Wi-Fi functionality for Azure Stack Edge Mini R has been deprecated. |
+|**29.**|Wi-Fi |Wi-Fi functionality for Azure Stack Edge Mini R has been deprecated. |  |
 
 ## Next steps
 

articles/databox-online/azure-stack-edge-gpu-install-update.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 04/01/2024
+ms.date: 04/02/2024
 ms.author: alkohli
 ---
 # Update your Azure Stack Edge Pro GPU 
@@ -30,9 +30,9 @@ The associated versions for this update are:
 - Device software version: Azure Stack Edge 2403 (3.2.2642.2453).
 - Device Kubernetes version: Azure Stack Kubernetes Edge 2403 (3.2.2642.2453).
 - Device Kubernetes workload profile: Other workloads.
-- Kubernetes server version: v1.26.3.
+- Kubernetes server version: v1.27.8.
 - IoT Edge version: 0.1.0-beta15.
-- Azure Arc version: 1.13.4.
+- Azure Arc version: 1.14.5.
 - GPU driver version: 535.104.05.
 - CUDA version: 12.2.
 
@@ -63,7 +63,7 @@ Supported update paths:
 
 If you have Azure Kubernetes service deployed and your Azure Stack Edge device and Kubernetes versions are either 2207 or 2209, you must update in multiple steps to apply 2403.
 
-Use the following steps to update your Azure Stack Edge version and Kubernetes version to 2312:
+Use the following steps to update your Azure Stack Edge version and Kubernetes version to 2403:
 
 1. Update your device version to 2303.
 1. Update your Kubernetes version to 2210.
@@ -86,7 +86,7 @@ The procedure to update an Azure Stack Edge is the same whether it's a single-no
 
 - **Single node** - For a single node device, installing an update or hotfix is disruptive and restarts your device. Your device will experience a downtime for the entire duration of the update.
 
-- **Two-node** - For a two-node cluster, this is an optimized update. The two-node cluster might experience short, intermittent disruptions while the update is in progress. We recommend that you shouldn't perform any operations on the device node when update is in progress. 
+- **Two-node** - For a two-node cluster, this is an optimized update. The two-node cluster might experience short, intermittent disruptions while the update is in progress. We recommend that you shouldn't perform any operations on the device node when an update is in progress. 
 
     The Kubernetes worker VMs goes down when a node goes down. The Kubernetes master VM fails over to the other node. Workloads continue to run. For more information, see [Kubernetes failover scenarios for Azure Stack Edge](azure-stack-edge-gpu-kubernetes-failover-scenarios.md).
 
@@ -117,12 +117,11 @@ Each of these steps is described in the following sections.
 
 ## Use the Azure portal
 
-We recommend that you install updates through the Azure portal. The device automatically scans for updates once a day. Once the updates are available, you see a notification in the portal. You can then download and install the updates.
+We recommend that you install updates through Azure portal. The device automatically scans for updates once a day. Once the updates are available, you see a notification in the portal. You can then download and install the updates.
 
 > [!NOTE]
 > - Make sure that the device is healthy and status shows as **Your device is running fine!** before you proceed to install the updates.
 
-
 Depending on the software version that you're running, install process might differ slightly. 
 
 - If you're updating from 2106 to 2110 or later, you'll have a one-click install. See the **version 2106 and later** tab for instructions.
@@ -278,7 +277,7 @@ This procedure takes around 20 minutes to complete. Perform the following steps
 
 5. The update starts. After the device is successfully updated, it restarts. The local UI isn't accessible in this duration.
 
-6. After the restart is complete, you're taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2312**. 
+6. After the restart is complete, you're taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2403**. 
 
 
 7. You'll now update the Kubernetes software version. Select the remaining two Kubernetes files together (file with the *Kubernetes_Package.0.exe* and *Kubernetes_Package.1.exe* suffix) and repeat the above steps to apply update.