Merge pull request #93613 from openshift-cherrypick-robot/cherry-pick-93583-to-enterprise-4.19

[enterprise-4.19] remove passive voice

Author: jeana-redhat

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

@@ -6,7 +6,7 @@
 [id="cpmso-yaml-provider-spec-aws_{context}"]
 = Sample AWS provider specification
 
-When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that is created by the installation program. You can omit any field that is set in the failure domain section of the CR.
+When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that the installation program creates. You can omit any field that is set in the failure domain section of the CR.
 
 In the following example, `<cluster_id>` is the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the OpenShift CLI installed, you can obtain the infrastructure ID by running the following command:
 

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

@@ -6,7 +6,7 @@
 [id="cpmso-yaml-provider-spec-gcp_{context}"]
 = Sample GCP provider specification
 
-When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that is created by the installation program. You can omit any field that is set in the failure domain section of the CR.
+When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that the installation program creates. You can omit any field that is set in the failure domain section of the CR.
 
 [discrete]
 [id="cpmso-yaml-provider-spec-gcp-oc_{context}"]

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

@@ -6,7 +6,7 @@
 [id="cpmso-yaml-provider-spec-nutanix_{context}"]
 = Sample Nutanix provider specification
 
-When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that is created by the installation program.
+When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that the installation program creates.
 
 [discrete]
 [id="cpmso-yaml-provider-spec-nutanix-oc_{context}"]

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

@@ -6,7 +6,7 @@
 [id="cpmso-yaml-provider-spec-openstack_{context}"]
 = Sample {rh-openstack} provider specification
 
-When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that is created by the installation program.
+When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that the installation program creates.
 
 .Sample OpenStack `providerSpec` values
 [source,yaml]

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

@@ -6,7 +6,7 @@
 [id="cpmso-yaml-provider-spec-vsphere_{context}"]
 = Sample VMware vSphere provider specification
 
-When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that is created by the installation program.
+When you create a control plane machine set for an existing cluster, the provider specification must match the `providerSpec` configuration in the control plane machine custom resource (CR) that the installation program creates.
 
 .Sample vSphere `providerSpec` values
 [source,yaml]