1237: merge overlapping subnet section into intro; improve VRF list page description

Author: Nadia-JSch

docs/infrastructure-management/ipam/subnets.mdx

@@ -8,7 +8,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 A subnet can be any Layer 3 network (IPv4 or IPv6) in your organization, and it can optionally be part of a VLAN. All IP addresses in Device42 must belong to a subnet.
 
-You can create nested subnets automatically and relocate manually created subnets as nested subnets. The subnet must be part of a [VRF group](vrf-groups.mdx) to create nested subnets.
+You can create nested subnets automatically and relocate manually created subnets as nested subnets. The subnet must be part of a [VRF group](vrf-groups.mdx) to create nested subnets. When you add an overlapping subnet within a VRF group, it is automatically positioned with the correct parent-child relationship.
 
 ## Subnet List Page
 
@@ -119,10 +119,6 @@ The **Subnet Category** field can be used to categorize your subnets. If you use
 
 If you mark the network or broadcast addresses as usable for a subnet, these IPs will appear as usable on the IP address list page.
 
-## VRF Groups and Overlapping Subnet Ranges
-
-When you add an overlapping subnet within a VRF group, the subnet is automatically positioned with the correct parent-child relationship.
-
 ## Add Nested Subnets
 
 Once you assign a VRF group to a subnet and save, a **Subnets** tab appears in the lower part of the page.

docs/infrastructure-management/ipam/vrf-groups.mdx

@@ -48,4 +48,4 @@ If you set a VRF group as the default, subnets and IPs are automatically assigne
   }}
 />
 
-The VRF group list page shows all your VRF groups.
+The list page shows all defined VRF groups with their associated subnets and details.