remove subnet size recommendation

Author: b-ahibbard

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -93,12 +93,8 @@ If you use a new VNet, you can create a subnet and delegate the subnet to Azure
 
 If the VNet is peered with another VNet, you can't expand the VNet address space. For that reason, the new delegated subnet needs to be created within the VNet address space. If you need to extend the address space, you must delete the VNet peering before expanding the address space.
 
->[!IMPORTANT]
-> Ensure the address space size of the Azure NetApp Files VNet is larger than its delegated subnet.
->
-> For example, if the delegated subnet is /24, the VNet address space containing the subnet must be /23 or larger. Noncompliance with this guideline can lead to unexpected issues in some traffic patterns: traffic traversing a hub-and-spoke topology that reaches Azure NetApp Files via a Network Virtual Appliance does not function properly. Additionally, this configuration can result in failures when creating SMB and CIFS (Common Internet File System) volumes if they attempt to reach DNS through hub-and-spoke network topology. 
->
-> It's also recommended that the size of the delegated subnet be at least /25 for SAP workloads and /26 for other workload scenarios.
+>[!NOTE]
+> It's recommended that the size of the delegated subnet be at least /25 for SAP workloads and /26 for other workload scenarios.
 
 ### <a name="udrs-and-nsgs"></a> User-defined routes (UDRs) and network security groups (NSGs)