Merge pull request #249183 from asudbring/vnet-update

Changed verbiage in steps to match portal changes

Author: prmerger-automator[bot]

articles/virtual-network/manage-virtual-network.md

@@ -2,12 +2,10 @@
 title: Create, change, or delete an Azure virtual network
 titlesuffix: Azure Virtual Network
 description: Create and delete a virtual network and change settings, like DNS servers and IP address spaces, for an existing virtual network.
-services: virtual-network
 author: asudbring
 ms.service: virtual-network
 ms.topic: how-to
-ms.workload: infrastructure-services
-ms.date: 11/16/2022
+ms.date: 08/23/2023
 ms.author: allensu
 ms.custom: template-how-to, engagement-fy23, devx-track-azurecli, devx-track-azurepowershell
 ---
@@ -51,7 +49,8 @@ The account you log into, or connect to Azure with, must be assigned to the [net
     | Name | Enter a name for the virtual network you're creating. | The name must be unique in the resource group that you select to create the virtual network in. <br> You can't change the name after the virtual network is created. <br> For naming suggestions, see [Naming conventions](/azure/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging#naming-and-tagging-resources). Following a naming convention can help make it easier to manage multiple virtual networks. |
     | Region | Select an Azure [region](https://azure.microsoft.com/regions/). | A virtual network can be in only one Azure region. However, you can connect a virtual network in one region to a virtual network in another region using [virtual network peering](virtual-network-peering-overview.md). <br> Any Azure resource that you connect to the virtual network must be in the same region as the virtual network. |
 
-1. Select **IP Addresses** tab or **Next: IP Addresses >**, and enter the following IP address information:
+1. Select **IP Addresses** tab or **Next: Security >**, **Next: IP Addresses >** and enter the following IP address information:
+   
    - **IPv4 Address space**: The address space for a virtual network is composed of one or more non-overlapping address ranges that are specified in CIDR notation. The address range you define can be public or private (RFC 1918). Whether you define the address range as public or private, the address range is reachable only from within the virtual network, from interconnected virtual networks, and from any on-premises networks that you've connected to the virtual network.
 
      You can't add the following address ranges: