Merge pull request #83705 from bergerhoffer/typos

Fixing a few typos

Author: bergerhoffer

modules/cnf-image-based-upgrade-seed-image-config.adoc

@@ -20,7 +20,7 @@ Therefore, the seed image generated from the seed cluster cannot contain any clu
 endif::[]
 
 ifdef::ibi[]
-You can create a seed image from a {sno} cluster with with the same hardware as your bare-metal host, and with a similar target cluster configuration. However, the seed image generated from the seed cluster cannot contain any cluster-specific configuration.
+You can create a seed image from a {sno} cluster with the same hardware as your bare-metal host, and with a similar target cluster configuration. However, the seed image generated from the seed cluster cannot contain any cluster-specific configuration.
 endif::[]
 
 The following table lists the components, resources, and configurations that you must and must not include in your seed image:

modules/cnf-running-the-performance-creator-profile-offline.adoc

@@ -6,7 +6,7 @@
 [id="running-the-performance-profile-creator-wrapper-script_{context}"]
 = Running the Performance Profile Creator wrapper script
 
-The wrapper script simplifies the process of creating a performance profile with the Performance Profile Creator (PPC) tool. The script handles tasks such as pulling and running the required container image, mounting directories into the container, and providing parameters directly to the container through Podman. 
+The wrapper script simplifies the process of creating a performance profile with the Performance Profile Creator (PPC) tool. The script handles tasks such as pulling and running the required container image, mounting directories into the container, and providing parameters directly to the container through Podman.
 
 For more information about the Performance Profile Creator arguments, see the section _"Performance Profile Creator arguments"_.
 
@@ -183,7 +183,7 @@ Flags:
 +
 [NOTE]
 ====
-You can optionally set a path for the Node Tuning Operator image using the `-p` option. If you do not set a path, the wrapper script uses the default image: `registry.redhat.io/openshift4/ose-cluster-node-tuning-rhel9-operator:vBranch Build`.
+You can optionally set a path for the Node Tuning Operator image using the `-p` option. If you do not set a path, the wrapper script uses the default image: `registry.redhat.io/openshift4/ose-cluster-node-tuning-rhel9-operator:v{product-version}`.
 ====
 
 . To display information about the cluster, run the PPC tool with the `log` argument by running the following command:
@@ -216,7 +216,7 @@ level=info msg="CPU(s): 4"
 level=info msg=---
 ----
 
-. Create a performance profile by running the following command. 
+. Create a performance profile by running the following command.
 +
 [source,terminal]
 ----

modules/deployment-plug-in-cluster.adoc

@@ -13,7 +13,7 @@ After pushing an image with your changes to a registry, you can deploy the plugi
 +
 [NOTE]
 ====
-You can specify additional parameters based on the needs of your plugin. The link:https://github.com/openshift/console-plugin-template/blob/main/charts/openshift-console-plugin/values.yaml[`values.yaml`] file provides a full set of suported parameters.
+You can specify additional parameters based on the needs of your plugin. The link:https://github.com/openshift/console-plugin-template/blob/main/charts/openshift-console-plugin/values.yaml[`values.yaml`] file provides a full set of supported parameters.
 ====
 
 .Procedure

modules/ibi-extra-manifests-standalone.adoc

@@ -1,18 +1,18 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/ibi-edge-image-based-install.adoc 
+// * edge_computing/ibi-edge-image-based-install.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="ibi-extra-manifest-standalone_{context}"]
 = Configuring resources for extra manifests
 
-You can optionally define additional resources in an image-based deployment for {sno} clusters. 
+You can optionally define additional resources in an image-based deployment for {sno} clusters.
 
 Create the additional resources in an `extra-manifests` folder in the same working directory that has the `install-config.yaml` and `image-based-config.yaml` manifests.
 
 == Creating a resource in the extra-manifests folder
 
-You can create a resource in the `extra-manifests` folder of your working directory to add extra manifests to the image-based deployment for {sno} clusters. 
+You can create a resource in the `extra-manifests` folder of your working directory to add extra manifests to the image-based deployment for {sno} clusters.
 
 The following example adds an single-root I/O virtualization (SR-IOV) network to the deployment.
 
@@ -22,7 +22,7 @@ The following example adds an single-root I/O virtualization (SR-IOV) network to
 
 .Procedure
 
-. Go to your working directory and create the `extra-manifests` folder by running the follow command:
+. Go to your working directory and create the `extra-manifests` folder by running the following command:
 +
 [source,terminal]
 ----

modules/installation-nutanix-config-yaml.adoc

@@ -256,7 +256,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
 ====
 <4> Optional: Provide additional configuration for the machine pool parameters for the compute and control plane machines.
 <5> Optional: Provide one or more pairs of a prism category key and a prism category value. These category key-value pairs must exist in Prism Central. You can provide separate categories to compute machines, control plane machines, or all machines.
-<6> TThe cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
+<6> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <7> Optional: Specify a project with which VMs are associated. Specify either `name` or `uuid` for the project type, and then provide the corresponding UUID or project name. You can associate projects to compute machines, control plane machines, or all machines.
 <8> Optional: By default, the installation program downloads and installs the {op-system-first} image. If Prism Central does not have internet access, you can override the default behavior by hosting the {op-system} image on any HTTP server or Nutanix Objects and pointing the installation program to the image.
 <9> For `<local_registry>`, specify the registry domain name, and optionally the port, that your mirror registry uses to serve content. For example `registry.example.com` or `registry.example.com:5000`. For `<credentials>`,

modules/installing-ocp-agent-ibm-z.adoc

@@ -17,49 +17,49 @@ Depending on your {ibm-z-name} environment, you can choose from the following op
 
 [NOTE]
 ====
-Currently, ISO boot support on {ibm-z-name} (`s390x``) is available only for {op-system-base-full} KVM, which provides the flexibility to choose either PXE or ISO-based installation. For installations with z/VM and Logical Partition (LPAR), only PXE boot is supported.
+Currently, ISO boot support on {ibm-z-name} (`s390x`) is available only for {op-system-base-full} KVM, which provides the flexibility to choose either PXE or ISO-based installation. For installations with z/VM and Logical Partition (LPAR), only PXE boot is supported.
 ====
 
 [id="networking-reqs-ibmz_{context}"]
 == Networking requirements for {ibm-z-title}
 
-In {ibm-z-title} environments, advanced networking technologies such as Open Systems Adapter (OSA), HiperSockets, and Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) require specific configurations that deviate from the standard network settings and those needs to be persisted for multiple boot scenarios that occur in the Agent-based Installation. 
+In {ibm-z-title} environments, advanced networking technologies such as Open Systems Adapter (OSA), HiperSockets, and Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) require specific configurations that deviate from the standard network settings and those needs to be persisted for multiple boot scenarios that occur in the Agent-based Installation.
 
 To persist these parameters during boot, the `ai.ip_cfg_override=1` parameter is required in the `paramline`. This parameter is used with the configured network cards to ensure a successful and efficient deployment on {ibm-z-title}.
 
 The following table lists the network devices that are supported on each hypervisor for the network configuration override functionality :
 
 [cols="3,2,2,2,2", options="header"]
 |====
-| Network device 
-| z/VM  
-| KVM 
-| LPAR Classic 
+| Network device
+| z/VM
+| KVM
+| LPAR Classic
 | LPAR Dynamic Partition Manager (DPM)
 
-| Virtual Switch 
+| Virtual Switch
 | Supported ^[1]^
-| Not applicable ^[2]^ 
-| Not applicable 
-| Not applicable 
+| Not applicable ^[2]^
+| Not applicable
+| Not applicable
 
-| Direct attached Open Systems Adapter (OSA) 
-| Supported 
+| Direct attached Open Systems Adapter (OSA)
+| Supported
 |  Not required ^[3]^
-| Supported 
-| Not required 
+| Supported
+| Not required
 
-| RDMA over Converged Ethernet (RoCE) 
-| Not required 
-| Not required 
-| Not required 
-| Not required 
+| RDMA over Converged Ethernet (RoCE)
+| Not required
+| Not required
+| Not required
+| Not required
 
-| HiperSockets 
-| Supported 
-| Not required 
-| Supported 
-| Not required 
+| HiperSockets
+| Supported
+| Not required
+| Supported
+| Not required
 |====
 . Supported: When the `ai.ip_cfg_override` parameter is required for the installation procedure.
 . Not Applicable: When a network card is not applicable to be used on the hypervisor.

modules/persistent-storage-csi-vsphere-disable-storage-overview.adoc

@@ -7,4 +7,4 @@
 [id="persistent-storage-csi-vsphere-disable-storage-overview_{context}"]
 = Disabling and enabling storage on vSphere
 
-Cluster administrators might want to disable the VMWare vSphere Container Storage Interface (CSI) Driver as a Day 2 operation, so the vSphere CSI Driver does not interface with your vSphere setup.
+Cluster administrators might want to disable the VMware vSphere Container Storage Interface (CSI) Driver as a Day 2 operation, so the vSphere CSI Driver does not interface with your vSphere setup.

modules/persistent-storage-csi-vsphere-multi-vcenter-support-overview.adoc

@@ -11,7 +11,7 @@ Deploying {product-title} across multiple vSphere vCenter clusters without share
 
 [NOTE]
 ====
-Multiple vCenters can only be configured *during* installation. Multiple vCenters *cannot* be be configured after installation.
+Multiple vCenters can only be configured *during* installation. Multiple vCenters *cannot* be configured after installation.
 ====
 
-The maximum number of supported vCenter clusters is three.
+The maximum number of supported vCenter clusters is three.

nodes/nodes/nodes-nodes-adding-node-iso.adoc

@@ -30,7 +30,7 @@ You can add nodes with this method in the following two ways:
 
 * Adding one or more nodes using a configuration file.
 +
-You can specify configurations for one or more nodes in the `nodes-config.yaml` file before running the the `oc adm node-image create` command.
+You can specify configurations for one or more nodes in the `nodes-config.yaml` file before running the `oc adm node-image create` command.
 This is useful if you want to add more than one node at a time, or if you are specifying complex configurations.
 
 * Adding a single node using only command flags.
@@ -49,4 +49,4 @@ include::modules/adding-node-iso-configs.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
-* xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#root-device-hints_ipi-install-installation-workflow[Root device hints]
+* xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#root-device-hints_ipi-install-installation-workflow[Root device hints]