Fix typos in docs

modules/builds-basic-start-source.adoc

@@ -8,7 +8,7 @@ Rather than relying on a Git source pull
 ifdef::openshift-origin,openshift-enterprise,openshift-dedicated[]
 or a Dockerfile
 endif::[]
-for a build, you can can also start a build by directly pushing your source, which could be the contents of a Git or SVN working directory, a set of prebuilt binary artifacts you want to deploy, or a single file. This can be done by specifying one of the following options for the `start-build` command:
+for a build, you can also start a build by directly pushing your source, which could be the contents of a Git or SVN working directory, a set of prebuilt binary artifacts you want to deploy, or a single file. This can be done by specifying one of the following options for the `start-build` command:
 
 [cols="1,2",options="header"]
 |===

modules/cluster-logging-elasticsearch-retention.adoc

@@ -15,7 +15,7 @@ determines when Elasticseach deletes the rolled-over indices.
 Elasticsearch rolls over an index, moving the current index and creating a new 
 index, when an index matches any of the following conditions:
 
-* The index is older than than the `rollover.maxAge` value in the Elasticsearch CR.
+* The index is older than the `rollover.maxAge` value in the Elasticsearch CR.
 * The index size is greater than 40 GB × the number of primary shards.
 * The index doc count is greater than 40960 KB × the number of primary shards.
 

modules/installation-gcp-service-account.adoc

@@ -26,7 +26,7 @@ See link:https://cloud.google.com/iam/docs/granting-roles-to-service-accounts#gr
 +
 [NOTE]
 ====
-While making the service account an Owner of the project is the easiest way to gain the required permissions, it means that that service account has complete control over the project. You must determine if the risk that comes from offering that power is acceptable.
+While making the service account an Owner of the project is the easiest way to gain the required permissions, it means that service account has complete control over the project. You must determine if the risk that comes from offering that power is acceptable.
 ====
 
 . Create the service account key in JSON format.

modules/installation-gcp-user-infra-config-host-project-vpc.adoc

@@ -27,7 +27,7 @@ See link:https://cloud.google.com/iam/docs/granting-roles-to-service-accounts#gr
 +
 [NOTE]
 ====
-While making the service account an Owner of the project is the easiest way to gain the required permissions, it means that that service account has complete control over the project. You must determine if the risk that comes from offering that power is acceptable.
+While making the service account an Owner of the project is the easiest way to gain the required permissions, it means that service account has complete control over the project. You must determine if the risk that comes from offering that power is acceptable.
 
 The service account for the project that hosts the shared VPC network requires the following roles:
 * Compute Network User

modules/installation-gcp-user-infra-shared-vpc-config-yaml.adoc

@@ -74,4 +74,4 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
 For production {product-title} clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your `ssh-agent` process uses.
 ====
 <8> How to publish the user-facing endpoints of your cluster. Set `publish` to `Internal` to deploy a private cluster, which cannot be accessed from the internet. The default value is `External`.
-To use a shared VPC in a cluster that uses infrastructure that you provision, you must set `publish` to `Internal`. The installation program will no longer be able to access the public DNS zone for the the base domain in the host project.
+To use a shared VPC in a cluster that uses infrastructure that you provision, you must set `publish` to `Internal`. The installation program will no longer be able to access the public DNS zone for the base domain in the host project.

modules/installation-osp-deleting-bootstrap-resources.adoc

@@ -33,4 +33,4 @@ $ ansible-playbook -i inventory.yaml down-03_bootstrap.yaml
 The bootstrap port, server, and floating IP address are deleted.
 
 [WARNING]
-If you did not disable the bootstrap Ignition file URL earlier,, do so now.
+If you did not disable the bootstrap Ignition file URL earlier, do so now.

modules/olm-deleting-operators-from-a-cluster-using-web-console.adoc

@@ -42,4 +42,4 @@ web console enables dashboards and navigation items for some Operators. To
 remove these after uninstalling the Operator, you might need to manually delete
 the Operator CRDs.
 
-. Select *Uninistall*. This Operator stops running and no longer receives updates.
+. Select *Uninstall*. This Operator stops running and no longer receives updates.

modules/olm-installing-from-operatorhub-using-cli.adoc

@@ -76,7 +76,7 @@ generate required RBAC access for all Operators in the same namespace as the
 OperatorGroup.
 +
 The namespace to which you subscribe the Operator must have an OperatorGroup
-that matches the the InstallMode of the Operator, either the `AllNamespaces` or
+that matches the InstallMode of the Operator, either the `AllNamespaces` or
 `SingleNamespace` mode. If the Operator you intend to install uses the
 `AllNamespaces`, then the `openshift-operators` namespace already has an
 appropriate OperatorGroup in place.

modules/olm-restricted-networks-configuring-operatorhub.adoc

@@ -131,7 +131,7 @@ to mirror, use the following steps to find them:
 search query. The output helps inform how you will later edit your `mapping.txt`
 file.
 +
-For example, to retrieve a list of images that that are similar to the string
+For example, to retrieve a list of images that are similar to the string
 `clusterlogging.4.3`:
 +
 [source,terminal]

modules/update-oc-configmap-signature-verification.adoc

@@ -22,7 +22,7 @@ If you are upgrading from a release prior to version 4.4.8, you must use the man
 
 . Use `oc` command-line interface (CLI) to log into the cluster that you are upgrading.
 
-. Apply the the mirrored release image signature ConfigMap to the connected cluster:
+. Apply the mirrored release image signature ConfigMap to the connected cluster:
 +
 [source,terminal]
 ----

storage/container_storage_interface/persistent-storage-csi-manila.adoc

@@ -15,7 +15,7 @@ To create CSI-provisioned PVs that mount to Manila storage assets, {product-titl
 
 * The _Manila CSI Driver Operator_ creates the required storage class that is needed to create PVCs for all available Manila share types. The Operator is installed in the `openshift-cluster-csi-drivers` namespace.
 
-* The _Manila CSI driver_ enables you to create and mount Manila PVs. The driver is installled in the `openshift-manila-csi-driver` namespace.
+* The _Manila CSI driver_ enables you to create and mount Manila PVs. The driver is installed in the `openshift-manila-csi-driver` namespace.
 
 include::modules/persistent-storage-csi-about.adoc[leveloffset=+1]