Update articles/vpn-gateway/vpn-gateway-classic-resource-manager-migration.md

Author: rmca14

articles/vpn-gateway/vpn-gateway-classic-resource-manager-migration.md

@@ -26,7 +26,7 @@ Once the VNet migration is completed, Azure will attempt to complete the remaind
 The Resource Manager model is different from the classic model and is composed of virtual network gateways, local network gateways and connection resources. These represent the VPN gateway itself, the local-site representing on premises address space and connectivity between the two respectively. Once migration is completed, your gateways won't be available in the classic model and all management operations on virtual network gateways, local network gateways, and connection objects must be performed using the Resource Manager model.
 
 ## Locating a classic VPN gateway 
-To locate a classic VPN gateway via PowerShell, you will need to install the Azure PowerShell Service Management module. Start here: [Installing the Azure PowerShell Service Management module](https://learn.microsoft.com/powershell/azure/servicemanagement/install-azure-ps). To view classic resources, you will need co-admin or owner permissions. You cannot use Az cmdlets to access classic resources. 
+To locate a classic VPN gateway via PowerShell, you will need to install the Azure PowerShell Service Management module. Start here: [Installing the Azure PowerShell Service Management module](https://learn.microsoft.com/powershell/azure/servicemanagement/install-azure-ps). To view classic resources, you will need co-admin or owner permissions. You can't use Az cmdlets to access classic resources. 
 
 
 To locate a classic VPN gateway via Azure portal, open the portal and search for "Virtual network(classic)". Select your classic virtual network and navigate to the gateway blade to find your classic virtual network gateway.