Merge pull request #22996 from bergerhoffer/master-build

Fixing typos to kick off a build

Author: bergerhoffer

modules/ipi-install-preparing-the-provision-node-for-openshift-install.adoc

@@ -24,7 +24,7 @@ Perform the following steps to prepare the environment.
 [root@provisioner ~]# su - kni -c "ssh-keygen -t rsa -f /home/kni/.ssh/id_rsa -N ''"
 ----
 
-. Log in in as the new user on the provision node.
+. Log in as the new user on the provision node.
 +
 ----
 # su - kni

modules/ipi-install-preparing-the-provisioner-node-for-openshift-install.adoc

@@ -26,7 +26,7 @@ Perform the following steps to prepare the environment.
 [root@provisioner ~]# su - kni -c "ssh-keygen -t rsa -f /home/kni/.ssh/id_rsa -N ''"
 ----
 
-. Log in in as the new user on the provision node.
+. Log in as the new user on the provision node.
 +
 ----
 [root@provisioner ~]# su - kni

modules/op-installing-pipelines-operator-in-web-console.adoc

@@ -29,7 +29,7 @@ Ensure that you do not select the *Community* version of the *OpenShift Pipeline
 
   .. Select *All namespaces on the cluster (default)* for the *Installation Mode*. This mode installs the Operator in the default `openshift-operators` namespace, which enables the Operator to watch and be made available to all namespaces in the cluster.
 
-  .. Select *Automatic* for the *Approval Strategy*. This ensures that the future upgrades to the Operator are handled automatically by the the Operator Lifecycle Manager (OLM). If you select the *Manual* approval strategy, OLM creates an update request. As a cluster administrator, you must then manually approve the OLM update request to update the Operator to the new version.
+  .. Select *Automatic* for the *Approval Strategy*. This ensures that the future upgrades to the Operator are handled automatically by the Operator Lifecycle Manager (OLM). If you select the *Manual* approval strategy, OLM creates an update request. As a cluster administrator, you must then manually approve the OLM update request to update the Operator to the new version.
   .. Select an *Update Channel*.
     *** The *ocp-<4.x>* channel enables installation of the latest stable release of the {pipelines-title} Operator.
     *** The *preview* channel enables installation of the latest preview version of the {pipelines-title} Operator, which may contain features that are not yet available from the 4.x update channel.

modules/topology-manager-policies.adoc

@@ -12,7 +12,7 @@ Topology Manager aligns Pod resources of all Quality of Service (QoS) classes by
 To align CPU resources with other requested resources in a Pod spec, the CPU Manager must be enabled with the `static` CPU Manager policy.
 ====
 
-Topology Manager supports four allocation policies, which you assign in the the `cpumanager-enabled` custom resource (CR):
+Topology Manager supports four allocation policies, which you assign in the `cpumanager-enabled` custom resource (CR):
 
 `none` policy::
 
@@ -32,7 +32,7 @@ For each container in a Pod with the `restricted` topology
 management policy, kubelet calls each Hint Provider to discover their resource
 availability. Using this information, the Topology Manager stores the
 preferred NUMA Node affinity for that container. If the affinity is not
-preferred, Topology Manager rejects this pod from the node, 
+preferred, Topology Manager rejects this pod from the node,
 resulting in a pod in a Terminated state with a pod admission failure.
 
 `single-numa-node` policy::

service_mesh/service_mesh_user_guide/ossm-traffic-manage.adoc

@@ -5,12 +5,12 @@ include::modules/ossm-document-attributes.adoc[]
 
 toc::[]
 
-You can control the flow of traffic and API calls between services in  {ProductName}. For example, some services in your service mesh may need to to communicate within the mesh and others may need to be hidden. Manage the traffic to hide specific backend services, expose services, create testing or versioning deployments, or add a security layer on a set of services. 
+You can control the flow of traffic and API calls between services in  {ProductName}. For example, some services in your service mesh may need to communicate within the mesh and others may need to be hidden. Manage the traffic to hide specific backend services, expose services, create testing or versioning deployments, or add a security layer on a set of services. 
 
-This guide references the Bookinfo sample application to provide examples of routing in an example application. Install the xref:../../service_mesh/service_mesh_day_two/ossm-example-bookinfo.adoc#ossm-bookinfo-tutorial[Bookinfo application] to learn how these routing examples work. 
+This guide references the Bookinfo sample application to provide examples of routing in an example application. Install the xref:../../service_mesh/service_mesh_day_two/ossm-example-bookinfo.adoc#ossm-bookinfo-tutorial[Bookinfo application] to learn how these routing examples work.
 
 include::modules/ossm-routing.adoc[leveloffset=+1]
 
 include::modules/ossm-routing-ingress.adoc[leveloffset=+1]
 
-include::modules/ossm-routing-bookinfo-example.adoc[leveloffset=+1]
+include::modules/ossm-routing-bookinfo-example.adoc[leveloffset=+1]

virt/virtual_machines/importing_vms/virt-importing-vmware-vm.adoc

@@ -14,7 +14,7 @@ include::modules/technology-preview.adoc[leveloffset=+1]
 
 == Creating and using a VMware Virtual Disk Development Kit image
 
-The VMware Virtual Disk Development Kit (VDDK) SDK is used to copy VMware virtual disks. You can create a VDDK image and add it to the the `v2v-vmware` ConfigMap to import a VMware virtual machine.
+The VMware Virtual Disk Development Kit (VDDK) SDK is used to copy VMware virtual disks. You can create a VDDK image and add it to the `v2v-vmware` ConfigMap to import a VMware virtual machine.
 
 You can store the VDDK image in the internal {product-title} image registry or in a secure external image registry.