replaces instances of VMware datacenter with two words

Author: jeana-redhat

modules/capi-yaml-machine-set-vsphere.adoc

@@ -40,10 +40,10 @@ spec:
           zone: <zone_a>
           server: <vcenter_server_name>
           topology:
-            datacenter: <region_a_datacenter>
-            computeCluster: "</region_a_datacenter/host/zone_a_cluster>"
-            resourcePool: "</region_a_datacenter/host/zone_a_cluster/Resources/resource_pool>"
-            datastore: "</region_a_datacenter/datastore/datastore_a>"
+            datacenter: <region_a_data_center>
+            computeCluster: "</region_a_data_center/host/zone_a_cluster>"
+            resourcePool: "</region_a_data_center/host/zone_a_cluster/Resources/resource_pool>"
+            datastore: "</region_a_data_center/datastore/datastore_a>"
             networks:
             - port-group
 ----

modules/capi-yaml-machine-template-vsphere.adoc

@@ -23,7 +23,7 @@ spec:
       server: <vcenter_server_ip> # <5>
       diskGiB: 128
       cloneMode: linkedClone # <6>
-      datacenter: <vcenter_datacenter_name> # <7>
+      datacenter: <vcenter_data_center_name> # <7>
       datastore: <vcenter_datastore_name> # <8>
       folder: <vcenter_vm_folder_path> # <9>
       resourcePool: <vsphere_resource_pool> # <10>
@@ -51,8 +51,8 @@ The following values are valid:
 +
 When using the `linkedClone` type, the disk size matches the clone source instead of using the `diskGiB` value.
 For more information, see the {vmw-short} documentation about VM clone types.
-<7> Specify the vCenter Datacenter to deploy the compute machine set on.
-<8> Specify the vCenter Datastore to deploy the compute machine set on.
+<7> Specify the vCenter data center to deploy the compute machine set on.
+<8> Specify the vCenter datastore to deploy the compute machine set on.
 <9> Specify the path to the vSphere VM folder in vCenter, such as `/dc1/vm/user-inst-5ddjd`.
 <10> Specify the vSphere resource pool for your VMs.
 <11> Specify the vSphere VM network to deploy the compute machine set to.

modules/configuring-vsphere-regions-zones.adoc

@@ -10,7 +10,7 @@
 :_mod-docs-content-type: PROCEDURE
 [id="configuring-vsphere-regions-zones_{context}"]
 = Configuring regions and zones for a VMware vCenter
-You can modify the default installation configuration file, so that you can deploy an {product-title} cluster to multiple vSphere datacenters that run in a single VMware vCenter.
+You can modify the default installation configuration file, so that you can deploy an {product-title} cluster to multiple vSphere data centers that run in a single VMware vCenter.
 
 The default `install-config.yaml` file configuration from the previous release of {product-title} is deprecated. You can continue to use the deprecated default configuration, but the `openshift-installer` will prompt you with a warning message that indicates the use of deprecated fields in the configuration file.
 
@@ -24,7 +24,7 @@ The example uses the `govc` command. The `govc` command is an open source comman
 +
 [IMPORTANT]
 ====
-You must specify at least one failure domain for your {product-title} cluster, so that you can provision datacenter objects for your VMware vCenter server. Consider specifying multiple failure domains if you need to provision virtual machine nodes in different datacenters, clusters, datastores, and other components. To enable regions and zones, you must define multiple failure domains for your {product-title} cluster.
+You must specify at least one failure domain for your {product-title} cluster, so that you can provision data center objects for your VMware vCenter server. Consider specifying multiple failure domains if you need to provision virtual machine nodes in different data centers, clusters, datastores, and other components. To enable regions and zones, you must define multiple failure domains for your {product-title} cluster.
 ====
 
 .Procedure
@@ -46,7 +46,7 @@ $ govc tags.category.create -d "OpenShift region" openshift-region
 $ govc tags.category.create -d "OpenShift zone" openshift-zone
 ----
 
-. To create a region tag for each region vSphere datacenter where you want to deploy your cluster, enter the following command in your terminal:
+. To create a region tag for each region vSphere data center where you want to deploy your cluster, enter the following command in your terminal:
 +
 [source,terminal]
 ----
@@ -60,23 +60,23 @@ $ govc tags.create -c <region_tag_category> <region_tag>
 $ govc tags.create -c <zone_tag_category> <zone_tag>
 ----
 
-. Attach region tags to each vCenter datacenter object by entering the following command:
+. Attach region tags to each vCenter data center object by entering the following command:
 +
 [source,terminal]
 ----
-$ govc tags.attach -c <region_tag_category> <region_tag_1> /<datacenter_1>
+$ govc tags.attach -c <region_tag_category> <region_tag_1> /<data_center_1>
 ----
 
-. Attach the zone tags to each vCenter datacenter object by entering the following command:
+. Attach the zone tags to each vCenter data center object by entering the following command:
 +
 [source,terminal]
 ----
-$ govc tags.attach -c <zone_tag_category> <zone_tag_1> /<datacenter_1>/host/vcs-mdcnc-workload-1
+$ govc tags.attach -c <zone_tag_category> <zone_tag_1> /<data_center_1>/host/vcs-mdcnc-workload-1
 ----
 
 . Change to the directory that contains the installation program and initialize the cluster deployment according to your chosen installation requirements.
 
-.Sample `install-config.yaml` file with multiple datacenters defined in a vSphere center
+.Sample `install-config.yaml` file with multiple data centers defined in a vSphere center
 
 [source,yaml]
 ----
@@ -100,32 +100,32 @@ platform:
     vcenters:
 ---
     datacenters:
-      - <datacenter1_name>
-      - <datacenter2_name>
+      - <data_center_1_name>
+      - <data_center_2_name>
     failureDomains:
     - name: <machine_pool_zone_1>
       region: <region_tag_1>
       zone: <zone_tag_1>
       server: <fully_qualified_domain_name>
       topology:
-        datacenter: <datacenter1>
-        computeCluster: "/<datacenter1>/host/<cluster1>"
+        datacenter: <data_center_1>
+        computeCluster: "/<data_center_1>/host/<cluster1>"
         networks:
         - <VM_Network1_name>
-        datastore: "/<datacenter1>/datastore/<datastore1>"
-        resourcePool: "/<datacenter1>/host/<cluster1>/Resources/<resourcePool1>"
-        folder: "/<datacenter1>/vm/<folder1>"
+        datastore: "/<data_center_1>/datastore/<datastore1>"
+        resourcePool: "/<data_center_1>/host/<cluster1>/Resources/<resourcePool1>"
+        folder: "/<data_center_1>/vm/<folder1>"
     - name: <machine_pool_zone_2>
       region: <region_tag_2>
       zone: <zone_tag_2>
       server: <fully_qualified_domain_name>
       topology:
-        datacenter: <datacenter2>
-        computeCluster: "/<datacenter2>/host/<cluster2>"
+        datacenter: <data_center_2>
+        computeCluster: "/<data_center_2>/host/<cluster2>"
         networks:
         - <VM_Network2_name>
-        datastore: "/<datacenter2>/datastore/<datastore2>"
-        resourcePool: "/<datacenter2>/host/<cluster2>/Resources/<resourcePool2>"
-        folder: "/<datacenter2>/vm/<folder2>"
+        datastore: "/<data_center_2>/datastore/<datastore2>"
+        resourcePool: "/<data_center_2>/host/<cluster2>/Resources/<resourcePool2>"
+        folder: "/<data_center_2>/vm/<folder2>"
 ---
 ----

modules/cpmso-yaml-failure-domain-vsphere.adoc

@@ -8,9 +8,9 @@
 
 On {vmw-full} infrastructure, the cluster-wide infrastructure Custom Resource Definition (CRD), `infrastructures.config.openshift.io`, defines failure domains for your cluster.
 The `providerSpec` in the `ControlPlaneMachineSet` custom resource (CR) specifies names for failure domains that the control plane machine set uses to ensure control plane nodes are deployed to the appropriate failure domain.
-A failure domain is an infrastructure resource made up of a control plane machine set, a vCenter datacenter, vCenter datastore, and a network.
+A failure domain is an infrastructure resource made up of a control plane machine set, a vCenter data center, vCenter datastore, and a network.
 
-By using a failure domain resource, you can use a control plane machine set to deploy control plane machines on  separate clusters or datacenters.
+By using a failure domain resource, you can use a control plane machine set to deploy control plane machines on  separate clusters or data centers.
 A control plane machine set also balances control plane machines across defined failure domains to provide fault tolerance capabilities to your infrastructure.
 
 [NOTE]

modules/cpmso-yaml-provider-spec-vsphere.adoc

@@ -41,7 +41,7 @@ spec:
             userDataSecret:
               name: master-user-data <9>
             workspace: <10>
-              datacenter: <vcenter_datacenter_name> <11>
+              datacenter: <vcenter_data_center_name> <11>
               datastore: <vcenter_datastore_name> <12>
               folder: <path_to_vcenter_vm_folder> <13>
               resourcePool: <vsphere_resource_pool> <14>
@@ -69,8 +69,8 @@ If you specify this value in the provider specification when using failure domai
 If the cluster is configured to use a failure domain, these parameters are configured in the failure domain.
 If you specify these values in the provider specification when using failure domains, the Control Plane Machine Set Operator ignores them.
 ====
-<11> Specifies the vCenter Datacenter for the control plane.
-<12> Specifies the vCenter Datastore for the control plane.
+<11> Specifies the vCenter data center for the control plane.
+<12> Specifies the vCenter datastore for the control plane.
 <13> Specifies the path to the vSphere VM folder in vCenter, such as `/dc1/vm/user-inst-5ddjd`.
 <14> Specifies the vSphere resource pool for your VMs.
 <15> Specifies the vCenter server IP or fully qualified domain name.

modules/images-configuration-registry-mirror.adoc

@@ -25,7 +25,7 @@ Setting up repository mirroring can be done in the following ways:
 
 * At {product-title} installation:
 +
-By pulling container images needed by {product-title} and then bringing those images behind your company's firewall, you can install {product-title} into a datacenter that is in a disconnected environment.
+By pulling container images needed by {product-title} and then bringing those images behind your company's firewall, you can install {product-title} into a data center that is in a disconnected environment.
 
 * After {product-title} installation:
 +
@@ -53,6 +53,6 @@ requested from the source repository.
 
 For new clusters, you can use IDMS, ITMS, and ICSP CRs objects as desired. However, using IDMS and ITMS is recommended.
 
-If you upgraded a cluster, any existing ICSP objects remain stable, and both IDMS and ICSP objects are supported. Workloads using ICSP objects continue to function as expected. However, if you want to take advantage of the fallback policies introduced in the IDMS CRs, you can migrate current workloads to IDMS objects by using the `oc adm migrate icsp` command as shown in the *Converting ImageContentSourcePolicy (ICSP) files for image registry repository mirroring* section that follows. Migrating to IDMS objects does not require a cluster reboot. 
+If you upgraded a cluster, any existing ICSP objects remain stable, and both IDMS and ICSP objects are supported. Workloads using ICSP objects continue to function as expected. However, if you want to take advantage of the fallback policies introduced in the IDMS CRs, you can migrate current workloads to IDMS objects by using the `oc adm migrate icsp` command as shown in the *Converting ImageContentSourcePolicy (ICSP) files for image registry repository mirroring* section that follows. Migrating to IDMS objects does not require a cluster reboot.
 
 include::snippets/idms-global-pull-secret.adoc[]

modules/installation-configuration-parameters.adoc

@@ -2692,7 +2692,7 @@ endif::vsphere[]
   vsphere:
     failureDomains:
       region:
-|If you define multiple failure domains for your cluster, you must attach the tag to each vCenter datacenter. To define a region, use a tag from the `openshift-region` tag category. For a single vSphere datacenter environment, you do not need to attach a tag, but you must enter an alphanumeric value, such as `datacenter`, for the parameter.
+|If you define multiple failure domains for your cluster, you must attach the tag to each vCenter data center. To define a region, use a tag from the `openshift-region` tag category. For a single vSphere data center environment, you do not need to attach a tag, but you must enter an alphanumeric value, such as `datacenter`, for the parameter.
 |String
 
 |platform:
@@ -2706,7 +2706,7 @@ endif::vsphere[]
   vsphere:
     failureDomains:
       zone:
-|If you define multiple failure domains for your cluster, you must attach a tag to each vCenter cluster. To define a zone, use a tag from the `openshift-zone` tag category. For a single vSphere datacenter environment, you do not need to attach a tag, but you must enter an alphanumeric value, such as `cluster`, for the parameter.
+|If you define multiple failure domains for your cluster, you must attach a tag to each vCenter cluster. To define a zone, use a tag from the `openshift-zone` tag category. For a single vSphere data center environment, you do not need to attach a tag, but you must enter an alphanumeric value, such as `cluster`, for the parameter.
 |String
 
 |platform:
@@ -2722,8 +2722,8 @@ endif::vsphere[]
     failureDomains:
       topology:
         datacenter:
-|Lists and defines the datacenters where {product-title} virtual machines (VMs) operate.
-The list of datacenters must match the list of datacenters specified in the `vcenters` field.
+|Lists and defines the data centers where {product-title} virtual machines (VMs) operate.
+The list of data centers must match the list of data centers specified in the `vcenters` field.
 |String
 
 ifdef::vsphere[]
@@ -2758,9 +2758,9 @@ endif::agent[]
     failureDomains:
       topology:
         folder:
-|Optional: The absolute path of an existing folder where the user creates the virtual machines, for example, `/<datacenter_name>/vm/<folder_name>/<subfolder_name>`.
+|Optional: The absolute path of an existing folder where the user creates the virtual machines, for example, `/<data_center_name>/vm/<folder_name>/<subfolder_name>`.
 ifdef::vsphere[]
-If you do not provide this value, the installation program creates a top-level folder in the datacenter virtual machine folder that is named with the infrastructure ID. If you are providing the infrastructure for the cluster and you do not want to use the default `StorageClass` object, named `thin`, you can omit the `folder` parameter from the `install-config.yaml` file.
+If you do not provide this value, the installation program creates a top-level folder in the data center virtual machine folder that is named with the infrastructure ID. If you are providing the infrastructure for the cluster and you do not want to use the default `StorageClass` object, named `thin`, you can omit the `folder` parameter from the `install-config.yaml` file.
 endif::vsphere[]
 |String
 
@@ -2778,9 +2778,9 @@ endif::vsphere[]
       topology:
         resourcePool:
 
-|Optional: The absolute path of an existing resource pool where the installation program creates the virtual machines, for example, `/<datacenter_name>/host/<cluster_name>/Resources/<resource_pool_name>/<optional_nested_resource_pool_name>`.
+|Optional: The absolute path of an existing resource pool where the installation program creates the virtual machines, for example, `/<data_center_name>/host/<cluster_name>/Resources/<resource_pool_name>/<optional_nested_resource_pool_name>`.
 ifdef::vsphere[]
-If you do not specify a value, the installation program installs the resources in the root of the cluster under `/<datacenter_name>/host/<cluster_name>/Resources`.
+If you do not specify a value, the installation program installs the resources in the root of the cluster under `/<data_center_name>/host/<cluster_name>/Resources`.
 endif::vsphere[]
 |String
 
@@ -2814,7 +2814,7 @@ endif::vsphere[]
   vsphere:
     vcenters:
       datacenters:
-|Lists and defines the datacenters where {product-title} virtual machines (VMs) operate. The list of datacenters must match the list of datacenters specified in the `failureDomains` field.
+|Lists and defines the data centers where {product-title} virtual machines (VMs) operate. The list of data centers must match the list of data centers specified in the `failureDomains` field.
 |String
 
 |platform:
@@ -2880,7 +2880,7 @@ endif::vsphere[]
 |platform:
   vsphere:
     datacenter:
-|Defines the datacenter where {product-title} virtual machines (VMs) operate.
+|Defines the data center where {product-title} virtual machines (VMs) operate.
 |String
 
 |platform:
@@ -2893,7 +2893,7 @@ endif::vsphere[]
   vsphere:
     folder:
 |Optional: The absolute path of an existing folder where the installation program creates the virtual machines. If you do not provide this value, the installation program creates a folder that is named with the infrastructure ID in the data center virtual machine folder.
-|String, for example, `/<datacenter_name>/vm/<folder_name>/<subfolder_name>`.
+|String, for example, `/<data_center_name>/vm/<folder_name>/<subfolder_name>`.
 
 ifdef::vsphere[]
 |platform:
@@ -2922,8 +2922,8 @@ endif::vsphere[]
 |platform:
   vsphere:
     resourcePool:
-|Optional: The absolute path of an existing resource pool where the installation program creates the virtual machines. If you do not specify a value, the installation program installs the resources in the root of the cluster under `/<datacenter_name>/host/<cluster_name>/Resources`.
-|String, for example, `/<datacenter_name>/host/<cluster_name>/Resources/<resource_pool_name>/<optional_nested_resource_pool_name>`.
+|Optional: The absolute path of an existing resource pool where the installation program creates the virtual machines. If you do not specify a value, the installation program installs the resources in the root of the cluster under `/<data_center_name>/host/<cluster_name>/Resources`.
+|String, for example, `/<data_center_name>/host/<cluster_name>/Resources/<resource_pool_name>/<optional_nested_resource_pool_name>`.
 
 |platform:
   vsphere:

modules/installation-initializing.adoc

@@ -333,7 +333,7 @@ The installation program connects to your vCenter instance.
 +
 [NOTE]
 ====
-After you create the installation configuration file, you can modify the file to create a multiple vSphere datacenters environment. This means that you can deploy an {product-title} cluster to multiple vSphere datacenters that run in a single VMware vCenter. For more information about creating this environment, see the section named _VMware vSphere region and zone enablement_.
+After you create the installation configuration file, you can modify the file to create a multiple vSphere data center environment. This means that you can deploy an {product-title} cluster to multiple vSphere data centers that run in a single VMware vCenter. For more information about creating this environment, see the section named _VMware vSphere region and zone enablement_.
 ====
 
 ... Select the default vCenter datastore to use.

modules/installation-installer-provisioned-vsphere-config-yaml.adoc

@@ -55,21 +55,21 @@ platform:
       region: <default_region_name>
       server: <fully_qualified_domain_name>
       topology:
-        computeCluster: "/<datacenter>/host/<cluster>"
-        datacenter: <datacenter>
-        datastore: "/<datacenter>/datastore/<datastore>" <6>
+        computeCluster: "/<data_center>/host/<cluster>"
+        datacenter: <data_center>
+        datastore: "/<data_center>/datastore/<datastore>" <6>
         networks:
         - <VM_Network_name>
-        resourcePool: "/<datacenter>/host/<cluster>/Resources/<resourcePool>" <7>
-        folder: "/<datacenter_name>/vm/<folder_name>/<subfolder_name>"
+        resourcePool: "/<data_center>/host/<cluster>/Resources/<resourcePool>" <7>
+        folder: "/<data_center_name>/vm/<folder_name>/<subfolder_name>"
         tagIDs: <8>
         - <tag_id>  <9>
       zone: <default_zone_name>
     ingressVIPs:
     - 10.0.0.2
     vcenters:
     - datacenters:
-      - <datacenter>
+      - <data_center>
       password: <password>
       port: 443
       server: <fully_qualified_domain_name>