Merge pull request #42773 from bergerhoffer/pr-42771-cp-49

[enterprise-4.9] Fixing some typos

Author: bergerhoffer

modules/eco-poison-pill-operator-about.adoc

@@ -6,9 +6,9 @@
 [id="about-poison-pill-operator_{context}"]
 = About the Poison Pill Operator
 
-The Poison Pill Operator runs on the cluster nodes and reboots nodes that are identified as unhealthy. The Operator uses the `MachineHealthCheck` controller to detect the health of a node in the cluster. When a node is identified as unhealthy, the `MachineHealthCheck` resource creates the `PoisonPillRemediation` custom resource (CR), which triggers the Poison Pill Operator. 
+The Poison Pill Operator runs on the cluster nodes and reboots nodes that are identified as unhealthy. The Operator uses the `MachineHealthCheck` controller to detect the health of a node in the cluster. When a node is identified as unhealthy, the `MachineHealthCheck` resource creates the `PoisonPillRemediation` custom resource (CR), which triggers the Poison Pill Operator.
 
-The Poison Pill Operator minimizes downtime for stateful applications and restores compute capacity if transient failures occur. You can use this Operator regardless of the management interface, such as IPMI or an API to provision a node, and regardless of of the cluster installation type, such as Installer Provisioned Infrastructure (IPI) or User Provisioned Infrastructure (UPI).
+The Poison Pill Operator minimizes downtime for stateful applications and restores compute capacity if transient failures occur. You can use this Operator regardless of the management interface, such as IPMI or an API to provision a node, and regardless of the cluster installation type, such as installer-provisioned infrastructure or user-provisioned infrastructure.
 
 [id="understanding-poison-pill-operator-config_{context}"]
 == Understanding the Poison Pill Operator configuration
@@ -31,7 +31,7 @@ spec:
   watchdogFilePath: /test/watchdog1 <2>
   isSoftwareRebootEnabled: true <3>
   apiServerTimeout: 15s <4>
-  apiCheckInterval: 5s <5>  
+  apiCheckInterval: 5s <5>
   maxApiErrorThreshold: 3 <6>
   peerApiServerTimeout: 5s <7>
   peerDialTimeout: 5s <8>
@@ -42,10 +42,10 @@ spec:
 <1> Specify the timeout duration for the surviving peer, after which the Operator can assume that an unhealthy node has been rebooted. The Operator automatically calculates the lower limit for this value. However, if different nodes have different watchdog timeouts, you must change this value to a higher value.
 <2> Specify the file path of the watchdog device in the nodes. If a watchdog device is unavailable, the `PoisonPillConfig` CR uses a software reboot.
 <3> Specify if you want to enable software reboot of the unhealthy nodes. By default, the value of `isSoftwareRebootEnabled` is set to `true`. To disable the software reboot, set the parameter value to `false`.
-<4> Specify the timeout duration to check connectivity with each API server. When this duration elapses, the Operator starts remediation. 
+<4> Specify the timeout duration to check connectivity with each API server. When this duration elapses, the Operator starts remediation.
 <5> Specify the frequency to check connectivity with each API server.
 <6> Specify a threshold value. After reaching this threshold, the node starts contacting its peers.
 <7> Specify the timeout duration to connect with the peer API server.
 <8> Specify the timeout duration for establishing connection with the peer.
 <9> Specify the timeout duration to get a response from the peer.
-<10> Specify the frequency to update peer information, such as IP address.
+<10> Specify the frequency to update peer information, such as IP address.

modules/installation-azure-user-infra-uploading-rhcos.adoc

@@ -129,4 +129,4 @@ ifeval::["{context}" == "installing-azure-user-infra"]
 endif::[]
 ifeval::["{context}" == "installing-azure-stack-hub-user-infra"]
 :!ash:
-endif::[]
+endif::[]

modules/kube-apiserver-operator.adoc

@@ -19,7 +19,7 @@ link:https://github.com/openshift/cluster-kube-apiserver-operator[openshift-kube
 == CRDs
 
 * `kubeapiservers.operator.openshift.io`
-** Scope: Cluser
+** Scope: Cluster
 ** CR: `kubeapiserver`
 ** Validation: Yes
 

modules/serverless-autoscaling-dashboard-navigating.adoc

@@ -6,7 +6,7 @@
 [id="serverless-autoscaling-dashboard-navigating_{context}"]
 = Navigating to the autoscaling dashboard
 
-You can use the following steps to navigate to the autoscaling dashboard in the the {product-title} web console.
+You can use the following steps to navigate to the autoscaling dashboard in the {product-title} web console.
 
 .Prerequisites