Merge pull request #234587 from oriwolman/patch-12

Update migration-classic-resource-manager-ps.md

Author: prmerger-automator[bot]

articles/virtual-machines/migration-classic-resource-manager-ps.md

@@ -7,7 +7,7 @@ ms.service: virtual-machines
 ms.subservice: classic-to-arm-migration
 ms.workload: infrastructure-services
 ms.topic: how-to
-ms.date: 01/25/2023
+ms.date: 04/14/2023
 ms.author: oriwolman 
 ms.custom: devx-track-azurepowershell compute-evergreen, devx-track-arm-template
 ---
@@ -226,10 +226,10 @@ To migrate virtual machines in a virtual network, you migrate the virtual networ
 > [!NOTE]
 > The virtual network name might be different from what is shown in the new portal. The new Azure portal displays the name as `[vnet-name]`, but the actual virtual network name is of type `Group [resource-group-name] [vnet-name]`. Before you start the migration, look up the actual virtual network name by using the command `Get-AzureVnetSite | Select -Property Name` or view it in the old Azure portal. 
 
-This example sets the virtual network name to **myVnet**. Replace the example virtual network name with your own.
+This following example sets the virtual network name to Group **[resource-group-name]** **[vnet-name]**.  Replace the example virtual network name with one that was returned from running the command in the **Note** section above..
 
 ```powershell
-    $vnetName = "myVnet"
+    $vnetName = "Group [resource-group-name] [vnet-name]"
 ```
 
 > [!NOTE]