updated to clear suggestions

Author: LouisBerner

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

@@ -38,7 +38,7 @@ The following table provides a summary of known issues in this release.
 | --- | --- | --- | --- |
 |**1.**|Preview features |For this release, the following features are available in preview: <br> - Clustering and Multi-Access Edge Computing (MEC) for Azure Stack Edge Pro GPU devices only.  <br> - VPN for Azure Stack Edge Pro R and Azure Stack Edge Mini R only. <br> - Local Azure Resource Manager, VMs, Cloud management of VMs, Kubernetes cloud management, and Multi-process service (MPS) for Azure Stack Edge Pro GPU, Azure Stack Edge Pro R, and Azure Stack Edge Mini R. |These features will be generally available in later releases. |
 |**2.**|HPN VMs |For this release, the Standard_F12_HPN can only support one network interface and can't be used for Multi-Access Edge Computing (MEC) deployments. | 
-|**3.**|Device capacity |If you update to this release from an older build, the device capacity doesn't show up in the Azure portal. If a VM is provisioned in the Azure portal, the capacity metrics are updated and displayed. |To sync the metrics on the Azure portal, create a VM and then delete it. | |
+|**3.**|Device capacity |If you update to this release from an older build, the device capacity doesn't show up in the Azure portal. If a VM is provisioned in the Azure portal, the capacity metrics are updated and displayed. |To sync the metrics on the Azure portal, create a VM and then delete it. |
 
 
 ## Known issues from previous releases

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

@@ -79,7 +79,7 @@ The following table provides a summary of known issues carried over from the pre
 |**23.**|Custom script VM extension |There's a known issue in the Windows VMs that were created in an earlier release and the device was updated to 2103. <br> If you add a custom script extension on these VMs, the Windows VM Guest Agent (Version 2.7.41491.901 only) gets stuck in the update causing the extension deployment to time out. | To work around this issue: <br> - Connect to the Windows VM using remote desktop protocol (RDP). <br> - Make sure that the `waappagent.exe` is running on the machine: `Get-Process WaAppAgent`. <br> - If the `waappagent.exe` isn't running, restart the `rdagent` service: `Get-Service RdAgent` \| `Restart-Service`. Wait for 5 minutes.<br> - While the `waappagent.exe` is running, kill the `WindowsAzureGuest.exe` process. <br> - After you kill the process, the process starts running again with the newer version. <br> - Verify that the Windows VM Guest Agent version is 2.7.41491.971 using this command: `Get-Process WindowsAzureGuestAgent` \| `fl ProductVersion`.<br> - [Set up custom script extension on Windows VM](azure-stack-edge-gpu-deploy-virtual-machine-custom-script-extension.md).  |
 |**24.**|Multi-Process Service (MPS) |When the device software and the Kubernetes cluster are updated, the MPS setting isn't retained for the workloads.   |[Re-enable MPS](azure-stack-edge-gpu-connect-powershell-interface.md#connect-to-the-powershell-interface) and redeploy the workloads that were using MPS. |
 |**25.**|Wi-Fi |Wi-Fi doesn't work on Azure Stack Edge Pro 2 in this release. | This functionality may be available in a future release.   |
-|**26.**|Device capacity |If you updated to this release from an older build, the device capacity didn't show up in the Azure portal. If a VM was provisioned in the Azure portal, the capacity metrics would update and display. |To sync the metrics on the Azure portal, create a VM and then delete it. | |
+|**26.**|Device capacity |If you updated to this release from an older build, the device capacity didn't show up in the Azure portal. If a VM was provisioned in the Azure portal, the capacity metrics would update and display. |To sync the metrics on the Azure portal, create a VM and then delete it. |
 
 
 ## Next steps