update

Author: mumian

articles/azure-resource-manager/bicep/scenarios-virtual-networks.md

@@ -19,7 +19,7 @@ Define your virtual networks by creating a resource with the type [`Microsoft.Ne
 Virtual networks contain subnets, which are logical groupings of IP addresses within the network. Subnets should always be managed as child resources, and the **subnets** property should never be defined within the virtual network resource. This approach ensures a safe and independent lifecycle for both resource types.
 
 > [!NOTE]
-> Microsoft has updated the Azure Virtual Network API to allow modifications to virtual networks without requiring the inclusion of the `subnet` property in PUT requests. Previously, omitting the `subnet` property would result in the deletion of existing subnets. With the new behavior, if the subnet property is not included in a PUT request, the existing subnets remain unchanged. Explicitly setting the subnet property to an empty value will delete all existing subnets, while providing specific subnet configurations will update or create subnets accordingly. This change simplifies virtual network management by preventing unintended subnet deletions during updates. For more information, see [Azure Virtual Network now supports updates without subnet property](https://techcommunity.microsoft.com/blog/azurenetworkingblog/azure-virtual-network-now-supports-updates-without-subnet-property/4067952).
+> The Azure Virtual Network API is updated to allow modifications to virtual networks without requiring the inclusion of the subnet property in PUT requests. Previously, omitting the subnet property would result in the deletion of existing subnets. With the new behavior, if the subnet property isn't included in a PUT request, the existing subnets remain unchanged. Explicitly setting the subnet property to an empty value deletes all existing subnets, while providing specific subnet configurations creates or updates subnets accordingly. This change simplifies virtual network management by preventing unintended subnet deletions during updates. For more information, see [Azure Virtual Network now supports updates without subnet property](https://techcommunity.microsoft.com/blog/azurenetworkingblog/azure-virtual-network-now-supports-updates-without-subnet-property/4067952).
 
 It's best to define your subnets as child resources, as in this example: