edit pass: quick-start-connect-vcenter-to-arc-using-script

Author: ShawnJackson

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

@@ -1,18 +1,18 @@
 ---
-title: Connect your VMware vCenter to Azure Arc by using the helper script
-description: In this quickstart, you'll learn how to use the helper script to connect your VMware vCenter to Azure Arc.
+title: Connect VMware vCenter Server to Azure Arc by using the helper script
+description: In this quickstart, you'll learn how to use the helper script to connect your VMware vCenter Server instance to Azure Arc.
 ms.topic: quickstart 
 ms.custom: references_regions
 ms.date: 11/10/2021
 
-# Customer intent: As a VI admin, I want to connect my vCenter to Azure to enable self-service through Azure Arc.
+# Customer intent: As a VI admin, I want to connect my vCenter Server instance to Azure to enable self-service through Azure Arc.
 ---
 
-# Quickstart: Connect your VMware vCenter to Azure Arc by using the helper script
+# Quickstart: Connect VMware vCenter Server to Azure Arc by using the helper script
 
-To start using the Azure Arc-enabled VMware vSphere (preview) features, you need to connect your VMware vCenter Server to Azure Arc. This quickstart shows you how to connect your VMware vCenter Server to Azure Arc by using a helper script.
+To start using the Azure Arc-enabled VMware vSphere (preview) features, you need to connect your VMware vCenter Server instance to Azure Arc. This quickstart shows you how to connect your VMware vCenter Server instance to Azure Arc by using a helper script.
 
-First, the script deploys a virtual appliance called [Azure Arc resource bridge (preview)](../resource-bridge/overview.md) in your vCenter environment. Then, it installs a VMware cluster extension to provide a continuous connection between your vCenter Server and Azure Arc.
+First, the script deploys a virtual appliance called [Azure Arc resource bridge (preview)](../resource-bridge/overview.md) in your vCenter environment. Then, it installs a VMware cluster extension to provide a continuous connection between vCenter Server and Azure Arc.
 
 > [!IMPORTANT]
 > In the interest of ensuring that new features are documented no later than their release, this page might include documentation for features that aren't yet publicly available.
@@ -29,7 +29,7 @@ First, the script deploys a virtual appliance called [Azure Arc resource bridge
 
 - vCenter Server running version 6.7.
 
-- Inbound connections allowed on TCP port (usually 443) so that the Azure Arc resource bridge and VMware cluster extension can communicate with the vCenter server.  
+- Inbound connections allowed on TCP port (usually 443) so that the Azure Arc resource bridge and VMware cluster extension can communicate with the vCenter Server instance.  
 
 - A resource pool or a cluster with a minimum capacity of 16 GB of RAM and four vCPUs.
 
@@ -38,7 +38,7 @@ First, the script deploys a virtual appliance called [Azure Arc resource bridge
 - An external virtual network/switch and internet access, directly or through a proxy.
 
 > [!NOTE]
-> Azure Arc-enabled VMware vSphere (preview) supports vCenters with a maximum of 2,500 virtual machines (VMs). If your vCenter has more than 2,500 VMs, we don't recommend that you use Arc-enabled VMware vSphere with it at this point.
+> Azure Arc-enabled VMware vSphere (preview) supports vCenter Server instances with a maximum of 2,500 virtual machines (VMs). If your vCenter Server instance has more than 2,500 VMs, we don't recommend that you use Arc-enabled VMware vSphere with it at this point.
 
 ### vSphere account
 
@@ -50,7 +50,7 @@ This account is used for the ongoing operation of Azure Arc-enabled VMware vSphe
 
 ### Workstation
 
-You need a Windows or Linux machine that can access both your vCenter Server and the internet, directly or through a proxy.
+You need a Windows or Linux machine that can access both your vCenter Server instance and the internet, directly or through a proxy.
 
 ## Prepare vCenter Server
 
@@ -68,7 +68,7 @@ You need a Windows or Linux machine that can access both your vCenter Server and
 
 4. In the **Platform** section, select **Add** under **VMware vCenter**.
 
-    :::image type="content" source="media/add-vmware-vcenter.png" alt-text="Screenshot that shows how to add a VMware vCenter through Azure Arc.":::
+    :::image type="content" source="media/add-vmware-vcenter.png" alt-text="Screenshot that shows how to add VMware vCenter through Azure Arc.":::
 
 5. Select **Create a new resource bridge**, and then select **Next**.
 
@@ -82,7 +82,7 @@ You need a Windows or Linux machine that can access both your vCenter Server and
 
 10. Leave **Use the same subscription and resource group as your resource bridge** selected.
 
-11. Provide a name for your vCenter in Azure. For example: **contoso-nyc-vcenter**.
+11. Provide a name for your vCenter Server instance in Azure. For example: **contoso-nyc-vcenter**.
 
 12. Select **Next: Download and run script**.
 
@@ -92,7 +92,7 @@ You need a Windows or Linux machine that can access both your vCenter Server and
 
 14. Based on the operating system of your workstation, download the PowerShell or Bash script and copy it to the [workstation](#prerequisites).
 
-15. If you want to see the status of your onboarding after you run the script on your workstation, select **Next: Verification**. Closing this page will not affect the onboarding.
+15. If you want to see the status of your onboarding after you run the script on your workstation, select **Next: Verification**. Closing this page won't affect the onboarding.
 
 ## Run the script
 
@@ -131,16 +131,16 @@ A typical onboarding that uses the script takes 30 to 60 minutes. During the pro
 | **Requirements** | **Details** |
 | --- | --- |
 | **Azure login** | [Sign in to Azure](https://www.microsoft.com/devicelogin) and enter the code when you're prompted. |
-| **vCenter FQDN/Address** | Enter the fully qualified domain name for the vCenter (or an IP address). For example: **10.160.0.1** or **nyc-vcenter.contoso.com**. |
+| **vCenter FQDN/Address** | Enter the fully qualified domain name for the vCenter Server instance (or an IP address). For example: **10.160.0.1** or **nyc-vcenter.contoso.com**. |
 | **vCenter Username** | Enter the username for the vSphere account. The required permissions for the account are listed in the [prerequisites](#prerequisites). |
 | **vCenter password** | Enter the password for the vSphere account. |
 | **Data center selection** | Select the name of the datacenter (as shown in the vSphere client) where the Azure Arc resource bridge's VM should be deployed. |
-| **Network selection** | Select the name of the virtual network or segment to which the VM must be connected. This network should allow the appliance to communicate with the vCenter server and the Azure endpoints (or internet). |
+| **Network selection** | Select the name of the virtual network or segment to which the VM must be connected. This network should allow the appliance to communicate with vCenter Server and the Azure endpoints (or internet). |
 | **Static IP / DHCP** | If you have DHCP server in your network and want to use it, enter **y**. Otherwise, enter **n**. </br>When you choose a static IP configuration, you're asked for the following information: </br> 1. **Static IP address prefix**: Network address in CIDR notation. For example: **192.168.0.0/24**. </br> 2. **Static gateway**: Gateway address. For example: **192.168.0.0**. </br> 3. **DNS servers**: Comma-separated list of DNS servers. </br> 4. **Start range IP**: Minimum size of two available IP addresses is required. One IP address is for the VM, and the other is reserved for upgrade scenarios. Provide the starting IP of that range. </br> 5. **End range IP**: Last IP address of the IP range requested in the previous field. </br> 6. **VLAN ID** (optional) |
 | **Resource pool** | Select the name of the resource pool to which the Azure Arc resource bridge's VM will be deployed. |
 | **Data store** | Select the name of the datastore to be used for the Azure Arc resource bridge's VM. |
 | **Folder** | Select the name of the vSphere VM and the template folder where the Azure Arc resource bridge's VM will be deployed. |
-| **VM template Name** | Provide a name for the VM template that will be created in your vCenter based on the downloaded OVA file. For example: **arc-appliance-template**. |
+| **VM template Name** | Provide a name for the VM template that will be created in your vCenter Server instance based on the downloaded OVA file. For example: **arc-appliance-template**. |
 | **Control Pane IP** | Provide a reserved IP address in your DHCP range, or provide a static IP address that's outside the DHCP range but still available on the network. Ensure that this IP address isn't assigned to any other machine on the network. |
 | **Appliance proxy settings** | Enter **y** if there's a proxy in your appliance network. Otherwise, enter **n**. </br> You need to populate the following boxes when you have proxy set up: </br> 1. **Http**: Address of the HTTP proxy server. </br> 2. **Https**: Address of the HTTPS proxy server. </br> 3. **NoProxy**: Addresses to be excluded from the proxy. </br> 4. **CertificateFilePath**: For SSL-based proxies, the path to the certificate to be used.