Update create-nsxt-segment-azure-portal-steps.md

Corrected VMware solution names.

Author: rvandenbedem

articles/azure-vmware/includes/create-nsxt-segment-azure-portal-steps.md

@@ -7,6 +7,14 @@ ms.date: 07/16/2021
 author: suzizuber
 ms.author: v-szuber
 ---
+title: Add an NSX-T Data Center network segment using Azure VMware Solution
+description: Steps to add an NSX-T Data Center network segment for Azure VMware Solution in the Azure portal.
+ms.topic: include
+ms.service: azure-vmware
+ms.date: 4/22/2023
+author: suzizuber
+ms.author: v-szuber
+---
 
 <!-- Used in configure-dhcp-azure-vmware-solution.md and tutorial-nsx-t-network-segment.md -->
 
@@ -18,19 +26,19 @@ ms.author: v-szuber
 
 2. Provide the details for the new logical segment and select **OK**.
 
-   :::image type="content" source="../media/networking/add-new-nsxt-segment.png" alt-text="Screenshot showing how to add a new NSX-T segment in the Azure portal.":::
+   :::image type="content" source="../media/networking/add-new-nsxt-segment.png" alt-text="Screenshot showing how to add a new NSX-T Data Center segment in the Azure portal.":::
 
-   - **Segment name** - Name of the segment that is visible in vCenter.
+   - **Segment name** - Name of the segment that is visible in vCenter Server.
 
    - **Subnet gateway** - Gateway IP address for the segment's subnet with a subnet mask. VMs are attached to a logical segment, and all VMs connecting to this segment belong to the same subnet.  Also, all VMs attached to this logical segment must carry an IP address from the same segment.
 
    - **DHCP** (optional) - DHCP ranges for a logical segment. You must configure a [DHCP server or DHCP relay](../configure-dhcp-azure-vmware-solution.md) to consume DHCP on Segments.    
 
    >[!NOTE]
-   >The **Connected gateway** is selected by default and is read-only.  It shows Tier-1 gateway and type of segment information. 
+   >The **Connected gateway** is selected by default and is read-only.  It shows Tier-1 Gateway and type of segment information. 
    >
-   >- **T1** - Name of the Tier-1 gateway in NSX-T Manager. A private cloud comes with an NSX-T Tier-0 gateway in Active/Active mode and a default NSX-T Tier-1 gateway in Active/Standby mode.  Segments created through the Azure VMware Solution console only connect to the default Tier-1 gateway, and the workloads of these segments get East-West and North-South connectivity. You can only create more Tier-1 gateways through NSX-T Manager. Tier-1 gateways created from the NSX-T Manager console are not visible in the Azure VMware Solution console. 
+   >- **T1** - Name of the Tier-1 Gateway in NSX-T Manager. A private cloud comes with an NSX-T Tier-0 Gateway in Active/Active mode and a default NSX-T Tier-1 Gateway in Active/Standby mode.  Segments created through the Azure VMware Solution console only connect to the default Tier-1 Gateway, and the workloads of these segments get East-West and North-South connectivity. You can only create more Tier-1 Gateways through NSX-T Manager. Tier-1 Gateways created from the NSX-T Manager console are not visible in the Azure VMware Solution console. 
    >
    >- **Type** - Overlay segment supported by Azure VMware Solution.
 
-The segment is now visible in Azure VMware Solution, NSX-T Manger, and vCenter.
+The segment is now visible in Azure VMware Solution, NSX-T Manager, and vCenter Server.