fixing language

Author: Sakthi Vetrivel

articles/openshift/howto-create-private-cluster.md

@@ -2,7 +2,7 @@
 title: Create a private cluster with Azure Red Hat OpenShift 3.11 | Microsoft Docs
 description: Create a private cluster with Azure Red Hat OpenShift 3.11
 author: klamenzo 
-ms.author: b-lejaku
+ms.author: suvetriv
 ms.service: container-service
 ms.topic: conceptual
 ms.date: 03/02/2020
@@ -17,15 +17,15 @@ keywords: aro, openshift, private cluster, red hat
 
 Private clusters provide the following benefits:
 
-* Private clusters do not expose cluster control plane components (such as the API servers) on a public IP address.
-* The VNet of a private cluster is configurable by customers, allowing you to set up networking to allow peering with other VNets, including ExpressRoute environments. You can also configure custom DNS on the VNet in order to integrate with internal services.
+* Private clusters don't expose cluster control plane components (such as the API servers) on a public IP address.
+* The virtual network of a private cluster is configurable by customers, allowing you to set up networking to allow peering with other virtual networks, including ExpressRoute environments. You can also configure custom DNS on the virtual network to integrate with internal services.
 
 ## Before you begin
 
 > [!NOTE]
 > This feature requires version 2019-10-27-preview of the ARO HTTP API. It is not yet supported in the Azure CLI.
 
-The fields in the following configuration snippet are new and must be included in your cluster configuration. `managementSubnetCidr` must be within the cluster VNet and is used by Azure to manage the cluster.
+The fields in the following configuration snippet are new and must be included in your cluster configuration. `managementSubnetCidr` must be within the cluster virtual network and is used by Azure to manage the cluster.
 
 ```
 properties:
@@ -37,13 +37,13 @@ properties:
 ```
 A private cluster can be deployed using the sample scripts provided below. Once the cluster is deployed, execute the `cluster get` command and view the `properties.FQDN` property to determine the private IP address of the OpenShift API server.
 
-The cluster VNet will have been created with permissions so that you can modify it. You can then setup networking to access the VNet (ExpressRoute, VPN, VNet peering) as required for your needs.
+The cluster virtual network will have been created with permissions so that you can modify it. You can then set up networking to access the virtual network (ExpressRoute, VPN, virtual network peering) as required for your needs.
 
-If you change the DNS nameservers on the cluster VNet, then you will need to issue an update on the cluster with the `properties.RefreshCluster` property set to `true` so that the VMs can be reimaged. This will allow them to pick up the new nameservers.
+If you change the DNS nameservers on the cluster virtual network, then you will need to issue an update on the cluster with the `properties.RefreshCluster` property set to `true` so that the VMs can be reimaged. This update will allow them to pick up the new nameservers.
 
 ## Sample Configuration Scripts
 
-Use the sample scripts in this section to setup and deploy your private cluster.
+Use the sample scripts in this section to set up and deploy your private cluster.
 
 ### Environment
 
@@ -97,7 +97,7 @@ Using the environment variables defined above, here is a sample cluster configur
            "osType": "Linux",
            "subnetCIDR": "10.0.0.0/24",
            "apiProperties": {
-            	"privateApiServer": true
+                "privateApiServer": true
             }
        },
        "agentPoolProfiles": [