Merge pull request #48617 from bergerhoffer/4.11typocheck

Typo fixes

Author: bergerhoffer

authentication/using-service-accounts-in-applications.adoc

@@ -16,9 +16,8 @@ include::modules/service-accounts-default.adoc[leveloffset=+1]
 
 * For information about requesting bound service account tokens, see xref:../authentication/bound-service-account-tokens.html#bound-sa-tokens-configuring_bound-service-account-tokens[Configuring bound service account tokens using volume projection]
 
-* For information about creating a service account token secret, see see xref:../nodes/pods/nodes-pods-secrets.html#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
+* For information about creating a service account token secret, see xref:../nodes/pods/nodes-pods-secrets.html#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
 
 include::modules/service-accounts-creating.adoc[leveloffset=+1]
 
 // include::modules/service-accounts-using-credentials-inside-a-container.adoc[leveloffset=+1]
-

cicd/pipelines/creating-applications-with-cicd-pipelines.adoc

@@ -76,7 +76,7 @@ include::modules/op-enabling-monitoring-of-event-listeners-for-triggers-for-user
 [id="pipeline-addtl-resources"]
 == Additional resources
 
-* To include pipelines as code along with with the application source code in the same repository, see xref:../../cicd/pipelines/using-pipelines-as-code.adoc#using-pipelines-as-code[Using Pipelines as code].
+* To include pipelines as code along with the application source code in the same repository, see xref:../../cicd/pipelines/using-pipelines-as-code.adoc#using-pipelines-as-code[Using Pipelines as code].
 * For more details on pipelines in the *Developer* perspective, see the xref:../../cicd/pipelines/working-with-pipelines-using-the-developer-perspective.adoc#working-with-pipelines-using-the-developer-perspective[working with pipelines in the *Developer* perspective] section.
 * To learn more about Security Context Constraints (SCCs), see the xref:../../authentication/managing-security-context-constraints.adoc#managing-pod-security-policies[Managing Security Context Constraints] section.
 * For more examples of reusable tasks, see the link:https://github.com/openshift/pipelines-catalog[OpenShift Catalog] repository. Additionally, you can also see the Tekton Catalog in the Tekton project.

logging/troubleshooting/cluster-logging-troubleshooting-for-critical-alerts.adoc

@@ -40,14 +40,14 @@ oc -n openshift-logging get pods -l component=elasticsearch
 
 . If some of the Elasticsearch nodes have not joined the cluster, perform the following steps.
 
-.. Confirm that Elasticsearch has an elected master node.
+.. Confirm that Elasticsearch has an elected control plane node.
 +
 [source,terminal]
 ----
 oc exec -n openshift-logging -c elasticsearch <elasticsearch_pod_name> -- es_util --query=_cat/master?v
 ----
 
-.. Review the pod logs of the elected master node for issues.
+.. Review the pod logs of the elected control plane node for issues.
 +
 [source,terminal]
 ----

modules/cnf-topology-aware-lifecycle-manager-troubleshooting.adoc

@@ -22,8 +22,8 @@ For more information about related topics, see the following documentation:
 
 You can determine the cause of the problem by reviewing the following questions:
 
-* Is the configuration that you are applying supported? 
-** Are the {rh-rhacm} and the {product-title} versions compatible? 
+* Is the configuration that you are applying supported?
+** Are the {rh-rhacm} and the {product-title} versions compatible?
 ** Are the {cgu-operator} and {rh-rhacm} versions compatible?
 * Which of the following components is causing the problem?
 ** <<talo-troubleshooting-managed-policies_{context}>>
@@ -33,15 +33,15 @@ You can determine the cause of the problem by reviewing the following questions:
 
 To ensure that the `ClusterGroupUpgrade` configuration is functional, you can do the following:
 
-. Create the `ClusterGroupUpgrade` CR with the `spec.enable` field set to `false`. 
+. Create the `ClusterGroupUpgrade` CR with the `spec.enable` field set to `false`.
 
-. Wait for the status to be updated and go through the troubleshooting questions. 
+. Wait for the status to be updated and go through the troubleshooting questions.
 
 . If everything looks as expected, set the `spec.enable` field to `true` in the `ClusterGroupUpgrade` CR.
 
 [WARNING]
 ====
-After you set the `spec.enable` field to `true` in the `ClusterUpgradeGroup` CR , the update procedure starts and you cannot edit the CR's `spec` fields anymore.
+After you set the `spec.enable` field to `true` in the `ClusterUpgradeGroup` CR, the update procedure starts and you cannot edit the CR's `spec` fields anymore.
 ====
 
 [id="talo-troubleshooting-modify-cgu_{context}"]
@@ -51,7 +51,7 @@ Issue:: You cannot edit the `ClusterUpgradeGroup` CR after enabling the update.
 
 Resolution:: Restart the procedure by performing the following steps:
 +
-. Remove the old `ClusterGroupUpgrade` CR by running the following command: 
+. Remove the old `ClusterGroupUpgrade` CR by running the following command:
 +
 [source,terminal]
 ----
@@ -117,7 +117,7 @@ default     policy4-common-sriov-sub-policy                      inform
 [discrete]
 == Checking policy compliance state
 
-Issue:: You want to check the compliance state of policies. 
+Issue:: You want to check the compliance state of policies.
 
 Resolution:: Run the following command:
 +

modules/dr-restoring-cluster-state.adoc

@@ -292,7 +292,7 @@ If the status is `Pending`, or the output lists more than one running etcd pod,
 For bare metal installations on installer-provisioned infrastructure, control plane machines are not recreated. For more information, see "Replacing a bare-metal control plane node".
 ====
 +
-If you are running installer-provisioned infrastructure, or you used the Machine API to create your machines, follow these steps. Otherwise, you must create the new master node using the same method that was used to originally create it.
+If you are running installer-provisioned infrastructure, or you used the Machine API to create your machines, follow these steps. Otherwise, you must create the new control plane node using the same method that was used to originally create it.
 +
 [WARNING]
 ====

modules/installation-configuration-parameters.adoc

@@ -1284,7 +1284,7 @@ Additional {rh-virtualization} configuration parameters for machine pools are de
 |Number
 
 |`<machine-pool>.platform.ovirt.vmType`
-|Optional. The VM workload type, such as `high-performance`, `server`, or `desktop`.  By default, master nodes use `high-performance`, and worker nodes use `server`. For details, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Virtual_Machine_General_settings_explained[Explanation of Settings in the New Virtual Machine and Edit Virtual Machine Windows] and link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Configuring_High_Performance_Virtual_Machines_Templates_and_Pools[Configuring High Performance Virtual Machines, Templates, and Pools] in the _Virtual Machine Management Guide_.
+|Optional. The VM workload type, such as `high-performance`, `server`, or `desktop`.  By default, control plane nodes use `high-performance`, and worker nodes use `server`. For details, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Virtual_Machine_General_settings_explained[Explanation of Settings in the New Virtual Machine and Edit Virtual Machine Windows] and link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Configuring_High_Performance_Virtual_Machines_Templates_and_Pools[Configuring High Performance Virtual Machines, Templates, and Pools] in the _Virtual Machine Management Guide_.
 [NOTE]
 ====
 `high_performance` improves performance on the VM, but there are limitations. For example, you cannot access the VM with a graphical console. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Configuring_High_Performance_Virtual_Machines_Templates_and_Pools[Configuring High Performance Virtual Machines, Templates, and Pools] in the _Virtual Machine Management Guide_.

modules/installation-nutanix-installer-infra-reqs.adoc

@@ -44,7 +44,7 @@ You must use AHV IP Address Management (IPAM) for the network and ensure that it
 
 [NOTE]
 ====
-It is recommended that each {product-title} node in the cluster have access to a Network Time Protocol (NTP) server that is discoverable via DHCP. Installation is possible without an NTP server. However, an NTP server prevents errors typically assoicated with asynchronous server clocks.
+It is recommended that each {product-title} node in the cluster have access to a Network Time Protocol (NTP) server that is discoverable via DHCP. Installation is possible without an NTP server. However, an NTP server prevents errors typically associated with asynchronous server clocks.
 ====
 
 [id="installation-nutanix-installer-infra-reqs-_{context}"]

modules/ldap-failover-configure-openshift.adoc

@@ -6,7 +6,7 @@
 = Configuring {product-title} to use SSSD as the basic remote authentication server
 
 Modify the default configuration of your cluster to use the new identity
-provider that you created. Complete the following steps on the first master host
+provider that you created. Complete the following steps on the first control plane host
 listed in the Ansible host inventory file.
 
 .Procedure

modules/mirror-registry-release-notes.adoc

@@ -7,7 +7,7 @@
 
 The _mirror registry for Red Hat OpenShift_ is a small and streamlined container registry that you can use as a target for mirroring the required container images of {product-title} for disconnected installations.
 
-These release notes track the development of the _mirror registry for Red Hat Openshift_ in {product-title}.
+These release notes track the development of the _mirror registry for Red Hat OpenShift_ in {product-title}.
 
 For an overview of the _mirror registry for Red Hat OpenShift_, see xref:../../installing/disconnected_install/installing-mirroring-creating-registry.html#mirror-registry-flags_installing-mirroring-creating-registry[Creating a mirror registry with mirror registry for Red Hat OpenShift].
 

modules/monitoring-supported-remote-write-authentication-settings.adoc

@@ -22,7 +22,7 @@ You cannot use this method simultaneously with authorization, OAuth 2.0, or basi
 
 |authorization|`authorization`|Authorization sets the `Authorization` header on every remote write request using the configured token.
 
-|OAuth 2.0|`oauth2`|An OAuth 2.0 configuration uses the client credentials grant type. 
+|OAuth 2.0|`oauth2`|An OAuth 2.0 configuration uses the client credentials grant type.
 Prometheus fetches an access token from `tokenUrl` with the specified client ID and client secret to access the remote write endpoint.
 You cannot use this method simultaneously with authorization, AWS Signature Version 4, or basic authentication.
 
@@ -50,12 +50,12 @@ data:
 ----
 <1> The URL of the remote write endpoint.
 <2> The required configuration details for the authentication method for the endpoint.
-Currently supported authentication methods are Amazon Web Services (AWS) Signature Version 4, authorization, basic authentication, OAuth 2.0, and TLS client. 
+Currently supported authentication methods are Amazon Web Services (AWS) Signature Version 4, authorization, basic authentication, OAuth 2.0, and TLS client.
 
 [NOTE]
 ====
 If you configure remote write for the Prometheus instance that monitors user-defined projects, edit the `user-workload-monitoring-config` config map in the `openshift-user-workload-monitoring` namespace.
-Note that the Prometheus config map component is called `prometheus` in the `user-workload-monitoring-config` `ConfigMap` object and not `prometheusK8s`, as it is in the `cluster-monitoring-config` `ConfigMap` object. 
+Note that the Prometheus config map component is called `prometheus` in the `user-workload-monitoring-config` `ConfigMap` object and not `prometheusK8s`, as it is in the `cluster-monitoring-config` `ConfigMap` object.
 ====
 
 == Example remote write authentication settings
@@ -111,13 +111,13 @@ data:
 <1> The AWS region.
 <2> The name of the `Secret` object containing the AWS API access credentials.
 <3> The key that contains the AWS API access key in the specified `Secret` object.
-<4> The key that contains teh AWS API secret key in the specified `Secret` object.
+<4> The key that contains the AWS API secret key in the specified `Secret` object.
 <5> The name of the AWS profile that is being used to authenticate.
 <6> The unique identifier for the Amazon Resource Name (ARN) assigned to your role.
 
 .Sample YAML for basic authentication
 
-The following shows sample basic authentication settings for a `Secret` object named `rw-basic-auth` in the `openshift-monitoring` namespace: 
+The following shows sample basic authentication settings for a `Secret` object named `rw-basic-auth` in the `openshift-monitoring` namespace:
 
 [source,yaml]
 ----
@@ -135,7 +135,7 @@ type: Opaque
 <2> The password.
 
 The following sample shows a `basicAuth` remote write configuration that uses a `Secret` object named `rw-basic-auth` in the `openshift-monitoring` namespace.
-It assumes that you have already set up authentication credentials for the endpoint. 
+It assumes that you have already set up authentication credentials for the endpoint.
 
 [source,yaml]
 ----
@@ -277,7 +277,7 @@ data:
   client.key: <client_key> <3>
 type: tls
 ----
-<1> The CA certificate in the Prometheus container with which to validate the server certificate. 
+<1> The CA certificate in the Prometheus container with which to validate the server certificate.
 <2> The client certificate for authentication with the server.
 <3> The client key.
 
@@ -311,4 +311,4 @@ data:
 <1> The name of the corresponding `Secret` object that contains the TLS authentication credentials. Note that `ca` and `cert` can alternatively refer to a `ConfigMap` object, though `keySecret` must refer to a `Secret` object.
 <2> The key in the specified `Secret` object that contains the CA certificate for the endpoint.
 <3> The key in the specified `Secret` object that contains the client certificate for the endpoint.
-<4> The key in the specified `Secret` object that contains the client key secret.
+<4> The key in the specified `Secret` object that contains the client key secret.