Merge pull request #2723 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-compute-docs (branch main)

Author: Taojunshen

articles/virtual-machines/deprecated-images.yml

@@ -35,7 +35,7 @@ sections:
           Before the scheduled deprecation date, you can continue to deploy new VM or scale set instances up until the deprecation date.
             After the scheduled deprecation date, you can't deploy new instances using the affected images. If the plan is scheduled for deprecation, all image versions within the plan are no longer available. If the entire offer is scheduled for deprecation, all plans within the offer are no longer available following deprecation.
           
-          - Active VM instances aren't impacted.  
+          - Existing VM instances aren't impacted.  
           - New VM instances can't be created from any of the impacted images.
           - Existing Virtual Machine Scale Set deployments can't be scaled out if configured with any of the impacted images. When a plan or offer is being deprecated, all existing scale sets deployments pinned to any image within the plan or offer respectively can't be scaled out.
           

articles/virtual-machines/maintenance-and-updates.md

@@ -55,7 +55,7 @@ The Azure platform triggers live migration in the following scenarios:
 
 Some planned-maintenance scenarios use live migration, and you can use Scheduled Events to know in advance when live migration operations will start. 
 
-Live migration can also be used to move VMs when Azure Machine Learning algorithms predict an impending hardware failure or when you want to optimize VM allocations. For more information about predictive modeling that detects instances of degraded hardware, see [Improving Azure VM resiliency with predictive machine learning and live migration](https://azure.microsoft.com/blog/improving-azure-virtual-machine-resiliency-with-predictive-ml-and-live-migration/?WT.mc_id=thomasmaurer-blog-thmaure). Live-migration notifications appear in the Azure portal in the Monitor and Service Health logs as well as in Scheduled Events if you use these services.
+Live migration can also be used to move VMs when Azure Machine Learning algorithms predict an impending hardware failure or VM allocations optimization. For more information about predictive modeling that detects instances of degraded hardware, see [Improving Azure VM resiliency with predictive machine learning and live migration](https://azure.microsoft.com/blog/improving-azure-virtual-machine-resiliency-with-predictive-ml-and-live-migration/?WT.mc_id=thomasmaurer-blog-thmaure). Live-migration notifications appear in the Azure portal in the Monitor and Service Health logs as well as in Scheduled Events if you use these services.
 
 
 

articles/virtual-machines/maintenance-configurations-cli.md

@@ -202,7 +202,7 @@ az maintenance assignment list \
    --provider-name Microsoft.Compute \
    --resource-group myMaintenanceRG \
    --resource-name myVMSS \
-   --resource-type virtualMachines \
+   --resource-type "virtualMachineScaleSets" \
    --query "[].{resource:resourceGroup, configName:name}" \
    --output table
 ```
@@ -265,7 +265,7 @@ az maintenance update list \
    --resource-name myHost \
    --resource-type hosts \
    --provider-name Microsoft.Compute \
-   --resource-parentname myHostGroup \
+   --resource-parent-name myHostGroup \
    --resource-parent-type hostGroups \
    --output table
 ```
@@ -317,7 +317,7 @@ az maintenance applyupdate create \
 
 ## Check the status of applying updates
 
-You can check on the progress of the updates by using `az maintenance applyupdate get`.
+You can check on the progress of the updates by using `az maintenance applyupdate show`.
 
 To see results for the last update, use `default` as the update name. Or replace `myUpdateName` with the name of the update that was returned when you ran `az maintenance applyupdate create`.
 
@@ -337,7 +337,7 @@ Type           : Microsoft.Maintenance/applyUpdates
 ### Isolated VM
 
 ```azurecli-interactive
-az maintenance applyupdate get \
+az maintenance applyupdate show \
    --subscription {subscriptionID} \ 
    --resource-group myMaintenanceRG \
    --resource-name myVM \
@@ -351,7 +351,7 @@ az maintenance applyupdate get \
 ### Dedicated host
 
 ```azurecli-interactive
-az maintenance applyupdate get \
+az maintenance applyupdate show \
    --subscription {subscriptionID} \ 
    --resource-group myMaintenanceRG \
    --resource-name myHost \
@@ -367,7 +367,7 @@ az maintenance applyupdate get \
 ### Virtual machine scale sets
 
 ```azurecli-interactive
-az maintenance applyupdate get \
+az maintenance applyupdate show \
    --subscription {subscriptionID} \ 
    --resource-group myMaintenanceRG \
    --resource-name myVMSS \