Merge pull request #91352 from rvandenbedem/patch-50

Update connect-multiple-private-clouds-same-region.md

Author: Jak-MS

articles/azure-vmware/connect-multiple-private-clouds-same-region.md

@@ -26,7 +26,7 @@ The Azure VMware Solution Interconnect feature is available in all regions.
 >[!NOTE]
 >The **AVS interconnect** feature doesn't check for overlapping IP space the way native Azure vNet peering does before creating the peering. Therefore, it's your responsibility to ensure that there isn't overlap between the private clouds.
 >
->In Azure VMware Solution environments, it's possible to configure non-routed, overlapping IP deployments on NSX segments that aren't routed to Azure.  These don't cause issues with the AVS Interconnect feature, as it only routes between the NSX T0 on each private cloud.
+>In Azure VMware Solution environments, it's possible to configure non-routed, overlapping IP deployments on NSX segments that aren't routed to Azure.  These don't cause issues with the AVS Interconnect feature, as it only routes between the NSX-T Data Center T0 gateway on each private cloud.
 
 
 ## Add connection between private clouds