Fixing some typos

Author: bergerhoffer

modules/cluster-logging-collector-log-forward-es.adoc

@@ -88,7 +88,7 @@ You can use a secret that contains a username and password to authenticate a sec
 
 For example, if you cannot use mutual TLS (mTLS) keys because a third party operates the Elasticsearch instance, you can use HTTP or HTTPS and set a secret that contains the username and password.
 
-. Create a `Secret` YAML file similar to the following example. Use base64-encoded values for the the `username` and `password` fields. The secret type is opaque by default.
+. Create a `Secret` YAML file similar to the following example. Use base64-encoded values for the `username` and `password` fields. The secret type is opaque by default.
 +
 [source,yaml]
 ----

modules/create-a-kubeletconfig-crd-to-edit-kubelet-parameters.adoc

@@ -11,7 +11,7 @@ The kubelet configuration is currently serialized as an Ignition configuration,
 
 [NOTE]
 ====
-As the fields in the `kubletConfig` object are passed directly to the kubelet from upstream Kubernetes, the kubelet validates those values directly. Invalid values in the `kubeletConfig` object might cause cluster nodes to become unavailable. For valid values, see the link:https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/[Kubernetes documentation].
+As the fields in the `kubeletConfig` object are passed directly to the kubelet from upstream Kubernetes, the kubelet validates those values directly. Invalid values in the `kubeletConfig` object might cause cluster nodes to become unavailable. For valid values, see the link:https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/[Kubernetes documentation].
 ====
 
 Consider the following guidance:

modules/manually-maintained-credentials-upgrade.adoc

@@ -57,7 +57,7 @@ It may take several minutes after adding the annotation for the upgradeable stat
 
 . Verify that the CCO is upgradeable:
 
-.. In the the *Administrator* perspective of the web console, navigate to *Administration* -> *Cluster Settings*.
+.. In the *Administrator* perspective of the web console, navigate to *Administration* -> *Cluster Settings*.
 
 .. To view the CCO status details, click *cloud-credential* in the *Cluster Operators* list.
 

modules/nw-ptp-configuring-linuxptp-services-as-boundary-clock.adoc

@@ -33,7 +33,7 @@ spec:
     ptp4lConf: | <6>
       [ens1f0] <7>
       masterOnly 0
-      [ens1f3] <8> 
+      [ens1f3] <8>
       masterOnly 1
       [global]
       #
@@ -136,7 +136,7 @@ spec:
       manufacturerIdentity  00:00:00
       userDescription         ;
       timeSource              0xA0
-    phc2sysOpts: "-a -r" <9> 
+    phc2sysOpts: "-a -r" <9>
   recommend: <10>
   - profile: "profile1" <11>
     priority: 10 <12>
@@ -187,7 +187,7 @@ linuxptp-daemon-tdspf           1/1     Running   0          43m   10.1.196.25
 ptp-operator-657bbb64c8-2f8sj   1/1     Running   0          43m   10.129.0.61      control-plane-1.example.com
 ----
 
-.. Check that the profile is correct. Examine the logs of the `linuxptp` daemon that corresponds to the node you specified in the `PtpConfig` profile. Run the folllowing command:
+.. Check that the profile is correct. Examine the logs of the `linuxptp` daemon that corresponds to the node you specified in the `PtpConfig` profile. Run the following command:
 +
 [source,terminal]
 ----
@@ -201,8 +201,8 @@ I1115 09:41:17.117596 4143292 daemon.go:107] in applyNodePTPProfile
 I1115 09:41:17.117604 4143292 daemon.go:109] updating NodePTPProfile to:
 I1115 09:41:17.117607 4143292 daemon.go:110] ------------------------------------
 I1115 09:41:17.117612 4143292 daemon.go:102] Profile Name: profile1
-I1115 09:41:17.117616 4143292 daemon.go:102] Interface:               
-I1115 09:41:17.117620 4143292 daemon.go:102] Ptp4lOpts: -s -2        
-I1115 09:41:17.117623 4143292 daemon.go:102] Phc2sysOpts: -a -r        
+I1115 09:41:17.117616 4143292 daemon.go:102] Interface:
+I1115 09:41:17.117620 4143292 daemon.go:102] Ptp4lOpts: -s -2
+I1115 09:41:17.117623 4143292 daemon.go:102] Phc2sysOpts: -a -r
 I1115 09:41:17.117626 4143292 daemon.go:116] ------------------------------------
-----
+----

modules/nw-ptp-configuring-linuxptp-services-as-ordinary-clock.adoc

@@ -80,7 +80,7 @@ linuxptp-daemon-tdspf           1/1     Running   0          43m   10.1.196.25
 ptp-operator-657bbb64c8-2f8sj   1/1     Running   0          43m   10.129.0.61      control-plane-1.example.com
 ----
 
-.. Check that the profile is correct. Examine the logs of the `linuxptp` daemon that corresponds to the node you specified in the `PtpConfig` profile. Run the folllowing command:
+.. Check that the profile is correct. Examine the logs of the `linuxptp` daemon that corresponds to the node you specified in the `PtpConfig` profile. Run the following command:
 +
 [source,terminal]
 ----
@@ -93,9 +93,9 @@ $ oc logs linuxptp-daemon-4xkbb -n openshift-ptp
 I1115 09:41:17.117596 4143292 daemon.go:107] in applyNodePTPProfile
 I1115 09:41:17.117604 4143292 daemon.go:109] updating NodePTPProfile to:
 I1115 09:41:17.117607 4143292 daemon.go:110] ------------------------------------
-I1115 09:41:17.117612 4143292 daemon.go:102] Profile Name: profile1  
-I1115 09:41:17.117616 4143292 daemon.go:102] Interface: ens787f1      
-I1115 09:41:17.117620 4143292 daemon.go:102] Ptp4lOpts: -s -2         
-I1115 09:41:17.117623 4143292 daemon.go:102] Phc2sysOpts: -a -r       
+I1115 09:41:17.117612 4143292 daemon.go:102] Profile Name: profile1
+I1115 09:41:17.117616 4143292 daemon.go:102] Interface: ens787f1
+I1115 09:41:17.117620 4143292 daemon.go:102] Ptp4lOpts: -s -2
+I1115 09:41:17.117623 4143292 daemon.go:102] Phc2sysOpts: -a -r
 I1115 09:41:17.117626 4143292 daemon.go:116] ------------------------------------
-----
+----

modules/ossm-supported-configurations.adoc

@@ -31,7 +31,7 @@ For additional information about {ProductName} lifecycle and supported configura
 
 {ProductName} supports the following network configurations.
 
-* Openshift-SDN
+* OpenShift-SDN
 * OVN-Kubernetes is supported as a technology preview in {product-title} version 4.7.
 
 [id="ossm-supported-configurations-kiali_{context}"]

modules/serverless-sinkbinding-odc.adoc

@@ -111,4 +111,4 @@ You can verify that the sink binding, sink, and cron job have been created and a
 +
 image::verify-sinkbinding-odc.png[View the sink binding and service in the Topology view]
 . Observe that successful jobs are being registered by the cron job once the sink binding is added. This means that the sink binding is successfully reconfiguring the jobs created by the cron job.
-. Browse the logs of the the `event-display` service pod to see events produced by the heartbeats cron job.
+. Browse the logs of the `event-display` service pod to see events produced by the heartbeats cron job.

networking/metallb/metallb-configure-services.adoc

@@ -78,7 +78,7 @@ If the address pool that you specify for `<address_pool_name>` does not exist, M
 == Accept any IP address
 
 By default, address pools are configured to permit automatic assignment.
-MetalLB assigns an an IP address from these address pools.
+MetalLB assigns an IP address from these address pools.
 
 To accept any IP address from any pool that is configured for automatic assignment, no special annotation or configuration is required.