Merge pull request #94585 from bergerhoffer/main-typo-check

Updating a bunch of typos

Author: bergerhoffer

disconnected/mirroring/about-installing-oc-mirror-v2.adoc

@@ -75,7 +75,7 @@ include::modules/oc-mirror-IDMS-ITMS-about.adoc[leveloffset=+1]
 // Configuring your cluster to use the resources generated by oc-mirror
 include::modules/oc-mirror-updating-cluster-manifests-v2.adoc[leveloffset=+2]
 
-After your cluster is configured to use the resources generated by oc-mirror plugin v2, see xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#next-steps_about-installing-oc-mirror-v2[Next Steps] for information about tasks that you can perform using your mirrored images.
+After your cluster is configured to use the resources generated by oc-mirror plugin v2, see xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#next-steps_about-installing-oc-mirror-v2[Next steps] for information about tasks that you can perform using your mirrored images.
 
 [role="_additional-resources"]
 .Additional resources
@@ -140,4 +140,4 @@ After you mirror images to your disconnected environment using oc-mirror plugin
 * xref:../../disconnected/using-olm.adoc#olm-restricted-networks[Using Operator Lifecycle Manager in disconnected environments]
 * xref:../../disconnected/updating/disconnected-update-osus.adoc#updating-disconnected-cluster-osus[Updating a cluster in a disconnected environment using the OpenShift Update Service]
 
-// Intentionally linking to the OSUS update procedure since we probably want to steer users to do that workflow as much as possible. But I can change to the index of the update section if I shouldn't be as prescriptive.
+// Intentionally linking to the OSUS update procedure since we probably want to steer users to do that workflow as much as possible. But I can change to the index of the update section if I shouldn't be as prescriptive.

edge_computing/day_2_core_cnf_clusters/telco-day-2-welcome.adoc

@@ -8,13 +8,13 @@ toc::[]
 
 You can use the following Day 2 operations to manage telco core CNF clusters.
 
-Updating a telco core CNF cluster:: Updating your cluster is a critical task that ensures that bugs and potential security vulnerabilities are patched. 
+Updating a telco core CNF cluster:: Updating your cluster is a critical task that ensures that bugs and potential security vulnerabilities are patched.
 For more information, see xref:../day_2_core_cnf_clusters/updating/telco-update-welcome.adoc#telco-update-welcome[Updating a telco core CNF cluster].
 
-Troubleshooting and maintaining telco core CNF clusters:: To maintain and troubleshoot a bare-metal environment where high-bandwidth network throughput is required, see see xref:../day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-intro.adoc#telco-troubleshooting-intro[Troubleshooting and maintaining telco core CNF clusters].
+Troubleshooting and maintaining telco core CNF clusters:: To maintain and troubleshoot a bare-metal environment where high-bandwidth network throughput is required, see xref:../day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-intro.adoc#telco-troubleshooting-intro[Troubleshooting and maintaining telco core CNF clusters].
 
-Observability in telco core CNF clusters:: {product-title} generates a large amount of data, such as performance metrics and logs from the platform and the workloads running on it. 
-As an administrator, you can use tools to collect and analyze the available data. 
+Observability in telco core CNF clusters:: {product-title} generates a large amount of data, such as performance metrics and logs from the platform and the workloads running on it.
+As an administrator, you can use tools to collect and analyze the available data.
 For more information, see xref:../day_2_core_cnf_clusters/observability/telco-observability.adoc#telco-observability[Observability in telco core CNF clusters].
 
 Security:: You can enhance security for high-bandwidth network deployments in telco environments by following key security considerations.

migration_toolkit_for_containers/mtc-migrating-vms.adoc

@@ -34,7 +34,7 @@ a|
 * Create a new persistent volume (PV) in the same namespace.
 * Copy data from the source PV to the target PV, and change the VM definition to point to the new PV.
 ** If you have the `liveMigrate` flag set, the VM migrates live.
-** If you do have the `liveMigrate` flag set, the VM shuts down, the source PV contents are copied to the target PV, and the the VM is started.
+** If you do have the `liveMigrate` flag set, the VM shuts down, the source PV contents are copied to the target PV, and the VM is started.
 
 |Move
 |No

modules/backing-up-the-backend-redis-database.adoc

@@ -76,7 +76,7 @@ spec:
 $ oc create -f redis-backup.yaml
 ----
 +
-.Example output:
+.Example output
 +
 [source,terminal]
 ----
@@ -93,7 +93,7 @@ backup.velero.io/redis-backup created
 $ oc get backups.velero.io redis-backup -o yaml
 ----
 +
-.Example output:
+.Example output
 +
 [source,terminal]
 ----
@@ -107,4 +107,4 @@ phase: Completed
 progress: {}
 startTimestamp: "2025-04-17T13:25:16Z"
 version: 1
-----
+----

modules/compliance-priorityclass.adoc

@@ -10,7 +10,7 @@ In large scale environments, the default `PriorityClass` object can be too low t
 
 .Prerequisites
 
-* Optional: You have created a `PriorityClass` object. For more information, see "Configuring priority and preemption" in the _Additional Resources_.
+* Optional: You have created a `PriorityClass` object. For more information, see "Configuring priority and preemption" in the _Additional resources_.
 
 .Procedure
 
@@ -55,4 +55,4 @@ roles:
 scanTolerations:
   - operator: Exists
 ----
-<1> If the `PriorityClass` referenced in the `ScanSetting` cannot be found, the Operator will leave the `PriorityClass` empty, issue a warning, and continue scheduling scans without a `PriorityClass`.
+<1> If the `PriorityClass` referenced in the `ScanSetting` cannot be found, the Operator will leave the `PriorityClass` empty, issue a warning, and continue scheduling scans without a `PriorityClass`.

modules/coreos-layering-configuring-on-remove.adoc

@@ -6,8 +6,8 @@
 [id="coreos-layering-configuring-on-remove_{context}"]
 = Removing an on-cluster custom layered image
 
-To prevent the custom layered images from taking up excessive space in your registry, you can automatically remove an on-cluster custom layered image from the repository by deleting the `MachineOSBuild` object that created the image. 
+To prevent the custom layered images from taking up excessive space in your registry, you can automatically remove an on-cluster custom layered image from the repository by deleting the `MachineOSBuild` object that created the image.
 
-The credentials provided by the registry push secret that you added to the the `MachineOSBuild` object must grant the permission for deleting an image from the registry. If the delete permission is not provided, the image is not removed when you delete the `MachineOSBuild` object.
+The credentials provided by the registry push secret that you added to the `MachineOSBuild` object must grant the permission for deleting an image from the registry. If the delete permission is not provided, the image is not removed when you delete the `MachineOSBuild` object.
 
 Note that the custom layered image is not deleted if the image is either currently in use on a node or is desired by the nodes, as indicated by the `machineconfiguration.openshift.io/currentConfig` or `machineconfiguration.openshift.io/desiredConfig` annotation on the node.

modules/cudn-status-conditions.adoc

@@ -200,7 +200,7 @@ h|Resolution
 |`Invalid value...When 2 CIDRs are set, they must be from different IP families`.
 |You must change one of your CIDR ranges to a different IP family.
 
-|The `spec.network.localnet.ipam.mode` is `Disabled` but the ``spec.network.localnet.lifecycle` has a value of `Persistent`.
+|The `spec.network.localnet.ipam.mode` is `Disabled` but the `spec.network.localnet.lifecycle` has a value of `Persistent`.
 |`lifecycle Persistent is only supported when ipam.mode is Enabled`
 |You must set the `ipam.mode` to `Enabled` when the optional field `lifecycle` has a value of `Persistent`.
 |===

modules/dr-restoring-etcd-quorum-ha.adoc

@@ -92,7 +92,7 @@ In a terminal that has access to the cluster as a `cluster-admin` user, run the
 $ oc get machines -n openshift-machine-api -o wide
 ----
 +
-.Example output:
+.Example output
 +
 [source,terminal]
 ----
@@ -123,7 +123,7 @@ A new machine is automatically provisioned after deleting the machine of the off
 $ oc get machines -n openshift-machine-api -o wide
 ----
 +
-.Example output:
+.Example output
 +
 [source,terminal]
 ----

modules/microshift-auto-recovery-example-bootc-systems.adoc

@@ -25,7 +25,7 @@ You must include the entire `auto-recovery` process for {op-system-image} system
 +
 [IMPORTANT]
 ====
-The location of the the `10-auto-recovery.conf` and `microshift-auto-recovery.service` must be relative to the Containerfile.
+The location of the `10-auto-recovery.conf` and `microshift-auto-recovery.service` must be relative to the Containerfile.
 
 For example, if the path to the Containerfile is `/home/microshift/my-build/Containerfile`, the systemd files need to be adjacent for proper embedding. The following paths are correct for this example:
 
@@ -90,4 +90,4 @@ $ sudo podman images "${IMAGE_NAME}"
 ----
 REPOSITORY                       TAG         IMAGE ID      CREATED        SIZE
 localhost/microshift-4.18-bootc  latest      193425283c00  2 minutes ago  2.31 GB
-----
+----

modules/microshift-config-parameters-table.adoc

@@ -67,7 +67,7 @@ The following table explains {microshift-short} configuration YAML parameters an
 
 |`debugging.logLevel`
 |`Normal`, `Debug`, `Trace`, or `TraceAll`
-|Log verbosity. Default value is is `Normal`.
+|Log verbosity. Default value is `Normal`.
 
 |`dns.baseDomain`
 |`valid domain`