From aa45ac4dbc88454e62dbdbf340a8202343ea3303 Mon Sep 17 00:00:00 2001
From: Preston Alvarado <700740+coolhome@users.noreply.github.com>
Date: Sun, 13 Aug 2023 12:42:39 -0400
Subject: [PATCH] Update New-AzVirtualNetworkSubnetConfig.md

`New-AzVirtualSubnetConfig` does not exists but `New-AzVirtualNetworkSubnetConfig` does.
---
 src/Network/Network/help/New-AzVirtualNetworkSubnetConfig.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/Network/Network/help/New-AzVirtualNetworkSubnetConfig.md b/src/Network/Network/help/New-AzVirtualNetworkSubnetConfig.md
index 426464859a8a..fc225bbde07b 100644
--- a/src/Network/Network/help/New-AzVirtualNetworkSubnetConfig.md
+++ b/src/Network/Network/help/New-AzVirtualNetworkSubnetConfig.md
@@ -69,8 +69,8 @@ New-AzVirtualNetwork -Name MyVirtualNetwork -ResourceGroupName TestResourceGroup
 ```
 
 This example creates two new subnet configurations using the 
-    New-AzVirtualSubnetConfig cmdlet, and then uses them to create a virtual network. 
-    The New-AzVirtualSubnetConfig template only creates an in-memory representation of 
+    New-AzVirtualNetworkSubnetConfig cmdlet, and then uses them to create a virtual network. 
+    The New-AzVirtualNetworkSubnetConfig template only creates an in-memory representation of 
     the subnet. In this example, the frontendSubnet has CIDR 10.0.1.0/24 and references a 
     network security group that allows RDP access. The backendSubnet has CIDR 10.0.2.0/24 and 
     references the same network security group.