Merge pull request #93243 from sharaths-cs/bw01

Minor editorial changes: changed purchase to provision, fixed typo, r…

Author: GitHubber17

articles/vmware-cloudsimple/cloudsimple-node.md

@@ -14,21 +14,21 @@ manager: dikamath
 Nodes are the building blocks of a Private Cloud. A node is:
 
 * A dedicated bare metal compute host where a VMware ESXi hypervisor is installed  
-* A unit of computing you can purchase or reserve to create Private Clouds
-* Available to purchase or reserve in a region where the CloudSimple service is available
+* A unit of computing you can provision or reserve to create Private Clouds
+* Available to provision or reserve in a region where the CloudSimple service is available
 
-You create a Private Cloud from the purchased nodes. To create a Private Cloud, you need a minimum of three nodes of the same SKU. To expand a Private Cloud, add additional nodes.  You can add nodes to an existing cluster or create a new cluster by purchasing nodes in the Azure portal and associating them with the CloudSimple service.  All purchased nodes are visible under the CloudSimple service.  
+You create a Private Cloud from the provisioned nodes. To create a Private Cloud, you need a minimum of three nodes of the same SKU. To expand a Private Cloud, add additional nodes.  You can add nodes to an existing cluster or create a new cluster by provisioning nodes in the Azure portal and associating them with the CloudSimple service.  All provisioned nodes are visible under the CloudSimple service.  
 
-## Purchased nodes
+## Provisioned nodes
 
-Purchased nodes provide pay-as-you-go capacity. Purchasing nodes helps you quickly scale your VMware cluster on demand. You can add nodes as needed or delete a purchased node to scale down your VMware cluster. Purchased nodes are billed on a monthly basis and charged to the subscription where they're purchased.
+Provisioned nodes provide pay-as-you-go capacity. Provisioning nodes helps you quickly scale your VMware cluster on demand. You can add nodes as needed or delete a provisioned node to scale down your VMware cluster. Provisioned nodes are billed on a monthly basis and charged to the subscription where they're provisioned.
 
 * If you pay for your Azure subscription by credit card, the card is billed immediately.
 * If you're billed by invoice, the charges appear on your next invoice.
 
 ## VMware Solution by CloudSimple nodes SKU
 
-The following types of nodes are available for purchase or reservation.
+The following types of nodes are available for provisioning or reservation.
 
 | SKU           | CS28 - Node                 | CS36 - Node                 | CS36m - Node                |
 |---------------|-----------------------------|-----------------------------|-----------------------------|
@@ -52,5 +52,5 @@ The following node limits apply to Private Clouds.
 
 ## Next steps
 
-* Learn how to [purchase nodes](create-nodes.md)
+* Learn how to [provision nodes](create-nodes.md)
 * Learn about [Private Clouds](cloudsimple-private-cloud.md)

articles/vmware-cloudsimple/create-cloudsimple-service.md

@@ -14,8 +14,9 @@ manager: dikamath
 
 To get started with Azure VMware Solution by CloudSimple, create the Azure VMware Solution by CloudSimple service in the Azure portal.
 
-> [!IMPORTANT]
-> Before you create the CloudSimple service, you must register the Microsoft.VMwareCloudSimple resource provider on your Azure subscription. Follow the steps in [Enable the Microsoft.VMwareCloudSimple resource provider on your Azure subscription](enable-cloudsimple-service.md).
+## Before you begin
+
+Allocate a /28 CIDR block for the gateway subnet. A gateway subnet is required per CloudSimple service and is unique to the region in which it's created. The gateway subnet is used for edge network services and requires a /28 CIDR block. The gateway subnet address space must be unique. It must not overlap with any network that communicates with the CloudSimple environment. The networks that communicate with CloudSimple include on-premises networks and Azure virtual networks.
 
 ## Sign in to Azure
 

articles/vmware-cloudsimple/create-private-cloud.md

@@ -26,6 +26,16 @@ Creating a Private Cloud helps you address a variety of common needs for network
 
 When you create a Private Cloud, you get a single vSphere cluster and all the management VMs that are created in that cluster.
 
+## Before you begin
+
+Nodes must be provisioned before you can create your Private Cloud. For more information on provisioning nodes, see [Provision nodes for Azure VMware Solution by CloudSimple](create-nodes.md).
+
+Allocate a CIDR range for vSphere/vSAN subnets for the Private Cloud. A Private Cloud is created as an isolated VMware stack environment (with ESXi hosts, vCenter, vSAN, and NSX) managed by a vCenter server. Management components are deployed in the network that is selected for vSphere/vSAN subnets CIDR. The network CIDR range is divided into different subnets during the deployment. The vSphere/vSAN subnet address space must be unique. It must not overlap with any network that communicates with the CloudSimple environment. The networks that communicate with CloudSimple include on-premises networks and Azure virtual networks. For more information on vSphere/vSAN subnets, see VLANs and subnets overview.
+
+* Minimum vSphere/vSAN subnets CIDR range prefix: /24
+* Maximum vSphere/vSAN subnets CIDR range prefix: /21
+
+
 ## Access the CloudSimple portal
 
 Access the [CloudSimple portal](access-cloudsimple-portal.md).
@@ -41,7 +51,7 @@ Access the [CloudSimple portal](access-cloudsimple-portal.md).
 
 5. In the CloudSimple portal, provide a name for your Private Cloud.
 6. Select **Location** for your Private Cloud.
-7. Select **Node type**, consistent with what you purchased on Azure.
+7. Select **Node type**, consistent with what you provisioned on Azure.
 8. Specify **Node count**.  At least three nodes are required to create a Private Cloud.
 
     ![Create Private Cloud - Basic info](media/create-private-cloud-basic-info.png)

articles/vmware-cloudsimple/on-premises-dns-setup.md

@@ -79,7 +79,7 @@ from the CloudSimple portal.
 A conditional forwarder forwards all DNS name resolution requests to the designated server. With this setup, any request to *.cloudsimple.io is forwarded to the DNS servers located on the Private Cloud. The following examples show how to set up
 forwarders on different types of DNS servers.
 
-### Create a conditional forwarded on a BIND DNS server
+### Create a conditional forwarder on a BIND DNS server
 
 The specific file and parameters to configure can vary based on your individual DNS setup.
 

articles/vmware-cloudsimple/quickstart-create-private-cloud.md

@@ -36,7 +36,7 @@ Private Clouds are managed through the CloudSimple portal. They have their own v
 
 5. In the CloudSimple portal, provide a name for your Private Cloud.
 6. Select the **Location** of your Private Cloud.
-7. Select **Node type**, consistent with what you purchased on Azure.
+7. Select **Node type**, consistent with what you provisioned on Azure.
 8. Specify **Node count**.  At least three nodes are required to create a Private Cloud.
 
     ![Create Private Cloud - Basic info](media/create-private-cloud-basic-info.png)