Merge pull request #250651 from b-hchen/patch-123

Consideration example statement: Change /26 to /23

Author: prmerger-automator[bot]

articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 09/05/2023
+ms.date: 09/07/2023
 ms.author: anfdocs
 ---
 # Delegate a subnet to Azure NetApp Files 
@@ -21,7 +21,7 @@ You must delegate a subnet to Azure NetApp Files. When you create a volume, you
 
 ## Considerations
 
-* The wizard for creating a new subnet defaults to a /24 network mask, which provides for 251 available IP addresses. You should consider a larger subnet (for example, /26 network mask) in scenarios such as SAP HANA where many volumes and storage endpoints are anticipated. You can also stay with the default network mask /24 as proposed by the wizard if you don't need to reserve many client or VM IP addresses in your Azure Virtual Network (VNet). Note that the network mask of the delegated network cannot be changed after the initial creation. 
+* The wizard for creating a new subnet defaults to a /24 network mask, which provides for 251 available IP addresses. You should consider a larger subnet (for example, /23 network mask) in scenarios such as SAP HANA where many volumes and storage endpoints are anticipated. You can also stay with the default network mask /24 as proposed by the wizard if you don't need to reserve many client or VM IP addresses in your Azure Virtual Network (VNet). Note that the network mask of the delegated network cannot be changed after the initial creation. 
 * In each VNet, only one subnet can be delegated to Azure NetApp Files.   
    Azure enables you to create multiple delegated subnets in a VNet.  However, any attempts to create a new volume will fail if you use more than one delegated subnet.  
    You can have only a single delegated subnet in a VNet. A NetApp account can deploy volumes into multiple VNets, each having its own delegated subnet.