incorporated review feedback

Author: ManikaDhiman

azure-local/known-issues.md

@@ -68,7 +68,7 @@ The following table lists the known issues in this release:
 | Update <!--33470082--> |  Solution update fails with the error: `Unable to install solution update "11.2506.1001.24" - Type 'UpdateFOD' of Role 'ComposedImageUpdate' raised an exception.` | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/SolutionUpdate-UpdateFOD.md). |
 | Deployment <!--33471589--> |  After Azure portal deployment, SConfig network settings shows the error: `Set-SCfNetworksetting : Cannot bind argument to parameter 'Value' because it is null.` | There's no known workaround in this release. |
 | Update <!--33448368--> |  Cluster-Aware Updating runs might fail with the error:<br>`Type 'SBEPartnerConfirmCauDone' of Role 'SBE' raised an exception:<br>SBE_MsftCIOnlyCommon_CommonForTesting_4.2.2504.16: ErrorID: SBE-CAU-RUNNING-AFTER-DONE -- CAU run is still in progress when it should be done. See https://aka.ms/AzureLocal/SBE/CauHelp for help. Review full Get-CauRun output it identify if it is progressing or stuck. Wait for it to complete if progressing.` | Wait for CAU run to complete (wait for `Get-CauRun` to report `RunNotInProgress`) and resume the update. |
-|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs and VHDs) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. | Create resources with a specified storage path. For more information, see [Troubleshoot Azure Local Virtual Machines enabled by Azure Arc](../azure-local/manage/troubleshoot-arc-enabled-vms.md#deployment-failure-due-to-insufficient-disk-space-on-the-first-storage-path). |
+|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs, data disks, and images) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. | Create resources with a specified storage path. For more information, see [Troubleshoot Azure Local Virtual Machines enabled by Azure Arc](../azure-local/manage/troubleshoot-arc-enabled-vms.md#resource-deployment-failure-due-to-insufficient-disk-space-on-the-first-storage-path). |
 
 ## Known issues from previous releases
 

azure-local/manage/troubleshoot-arc-enabled-vms.md

@@ -186,7 +186,7 @@ To resolve this issue, follow these steps:
 
 1. Restart the VM. After the restart, the warning message should no longer appear.
 
-## Deployment failure due to insufficient disk space on the first storage path
+## Resource deployment failure due to insufficient disk space on the first storage path
 
 **Error:**
 
@@ -198,17 +198,15 @@ If no storage path is specified during deployment, resources are automatically p
 
 **Resolution:**
 
-When creating a VM or VHD, choose a storage path manually.
+When creating a VM, data disk, or image, choose a storage path manually.
 
 # [Azure portal](#tab/azure-portal)
 
-When creating a VM in the Azure portal, select the **Choose manually** option for storage path and then select a storage path from the available list.
-
-When attaching data disks to the VM, select the **Choose manually** option for storage path allocation method and then select a storage path from the available list.
+When creating an image, select the **Choose manually** option for storage path and then select a storage path from the available list.
 
 # [CLI](#tab/cli)
 
-To specify a storage path when creating a VM or VHD, use the `--storage-path-id` parameter with the `az stack-hci-vm create` or `az stack-hci-vm disk create` command.
+To specify a storage path when creating a VM, data disk, or image, use the `--storage-path-id` parameter with the `az stack-hci-vm create`, `az stack-hci-vm disk create`, or `az stack-hci-vm image create` command.
 
 # [ARM template](#tab/arm-template)