Merge pull request #28383 from bergerhoffer/openshift-typos

bergerhoffer · web-flow · commit d755e7dee70f · 2021-01-06T13:56:14.000-05:00
Fixing some typos
diff --git a/modules/cluster-logging-visualizer-indices.adoc b/modules/cluster-logging-visualizer-indices.adoc
@@ -11,7 +11,7 @@ An index pattern defines the Elasticsearch indices that you want to visualize. T
 
 * A user must have the `cluster-admin` role, the `cluster-reader` role, or both roles to view the *infra* and *audit* indices in Kibana. The default `kubeadmin` user has proper permissions to view these indices.
 +
-If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access the these indices. You can use the following command to check if the current user has appropriate permissions:
+If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access these indices. You can use the following command to check if the current user has appropriate permissions:
 +
 [source,terminal]
 ----
diff --git a/modules/cluster-logging-visualizer-kibana.adoc b/modules/cluster-logging-visualizer-kibana.adoc
@@ -13,9 +13,9 @@ You view cluster logs in the Kibana web console. The methods for viewing and vis
 
 * Kibana index patterns must exist.
 
-* A user must have the `cluster-admin` role, the `cluster-reader` role, or both roles to view the *infra* and *audit* indices in Kibana. The default `kubeadmin` user has proper permissions to view these indices. 
+* A user must have the `cluster-admin` role, the `cluster-reader` role, or both roles to view the *infra* and *audit* indices in Kibana. The default `kubeadmin` user has proper permissions to view these indices.
 +
-If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access the these indices. You can use the following command to check if the current user has appropriate permissions:
+If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access these indices. You can use the following command to check if the current user has appropriate permissions:
 +
 [source,terminal]
 ----
diff --git a/modules/cluster-logging-visualizer-launch.adoc b/modules/cluster-logging-visualizer-launch.adoc
@@ -10,9 +10,9 @@ pie charts, heat maps, built-in geospatial support, and other visualizations.
 
 .Prerequisites
 
-* To list the *infra* and *audit* indices in Kibana, a user must have the `cluster-admin` role, the `cluster-reader` role, or both roles. The default `kubeadmin` user has proper permissions to list these indices. 
+* To list the *infra* and *audit* indices in Kibana, a user must have the `cluster-admin` role, the `cluster-reader` role, or both roles. The default `kubeadmin` user has proper permissions to list these indices.
 +
-If you can view the pods and logs in the `default`, `kube-*` and `openshift-*` projects, you should be able to access the these indices. You can use the following command to check if the current user has proper permissions:
+If you can view the pods and logs in the `default`, `kube-*` and `openshift-*` projects, you should be able to access these indices. You can use the following command to check if the current user has proper permissions:
 +
 [source,terminal]
 ----
@@ -44,4 +44,3 @@ The Kibana interface launches.
 ====
 If you get a *security_exception* error in the Kibana console and cannot access your Kibana indices, you might have an expired OAuth token. If you see this error, log out of the Kibana console, and then log back in. This refreshes your OAuth tokens and you should be able to access your indices.
 ====
-
diff --git a/modules/ipi-install-additional-install-config-parameters.adoc b/modules/ipi-install-additional-install-config-parameters.adoc
@@ -143,7 +143,7 @@ a|`provisioningNetworkCIDR`
 
 |`bootstrapProvisioningIP`
 |The second IP address of the `provisioningNetworkCIDR`.
-|The IP on the bootstrap VM where the provisioning services run while the the installer is deploying the control plane (master) nodes. Defaults to the second IP of the `provisioning` subnet. For example, `172.22.0.2`
+|The IP on the bootstrap VM where the provisioning services run while the installer is deploying the control plane (master) nodes. Defaults to the second IP of the `provisioning` subnet. For example, `172.22.0.2`
 ifdef::upstream[]
 ifeval::[{release} >= 4.5]
 or `2620:52:0:1307::2`
diff --git a/modules/nodes-scheduler-default-creating.adoc b/modules/nodes-scheduler-default-creating.adoc
@@ -89,7 +89,7 @@ For example:
 $ oc patch Scheduler cluster --type='merge' -p '{"spec":{"policy":{"name":"scheduler-policy"}}}' --type=merge
 ----
 +
-After making the change to the `Scheduler` config resource, wait for the `opensift-kube-apiserver` pods to redeploy. This can take several minutes. Until the pods redeploy, new scheduler does not take effect.
+After making the change to the `Scheduler` config resource, wait for the `openshift-kube-apiserver` pods to redeploy. This can take several minutes. Until the pods redeploy, new scheduler does not take effect.
 
 . Verify the scheduler policy is configured by viewing the log of a scheduler pod in the `openshift-kube-scheduler` namespace. The following command checks for the predicates and priorities that are being registered by the scheduler:
 +
diff --git a/modules/nodes-scheduler-node-selectors-cluster.adoc b/modules/nodes-scheduler-node-selectors-cluster.adoc
@@ -12,7 +12,7 @@ the pod on nodes with matching labels.
 
 You configure cluster-wide node selectors by creating a Scheduler Operator custom resource (CR). You add labels to a node by editing a `Node` object, a `MachineSet` object, or a `MachineConfig` object. Adding the label to the machine set  ensures that if the node or machine goes down, new nodes have the label. Labels added to a node or machine config do not persist if the node or machine goes down.
 
-For example, the the Scheduler configures the cluster-wide `region=east` node selector:
+For example, the Scheduler configures the cluster-wide `region=east` node selector:
 
 .Example Scheduler Operator custom resource
 [source,yaml]
diff --git a/modules/serverless-config-replicas.adoc b/modules/serverless-config-replicas.adoc
@@ -5,7 +5,7 @@
 [id="serverless-config-replicas_{context}"]
 = Configuring high availability replicas on {ServerlessProductName}
 
-High availability (HA) functionality is available by default on {ServerlessProductName} for the `autoscaler-hpa`, `controller`, `activator` , `kourier-control`, and `kourier-gateway` controllers. These components are configured with two replicas by default.
+High availability (HA) functionality is available by default on {ServerlessProductName} for the `autoscaler-hpa`, `controller`, `activator`, `kourier-control`, and `kourier-gateway` controllers. These components are configured with two replicas by default.
 
 You modify the number of replicas that are created per controller by changing the configuration of `KnativeServing.spec.highAvailability` in the KnativeServing custom resource definition.
 // This field also specifies the minimum number of _activators_ if you are using the horizontal pod autoscaler (HPA). For more information about HPA, see
diff --git a/modules/troubleshooting-disabling-autoreboot-mco.adoc b/modules/troubleshooting-disabling-autoreboot-mco.adoc
@@ -3,7 +3,7 @@
 // * support/troubleshooting/troubleshooting-operator-issues.adoc
 
 [id="troubleshooting-disabling-autoreboot-mco_{context}"]
-= Disabling Machine Config Operator from automatically rebooting	
+= Disabling Machine Config Operator from automatically rebooting
 
 When configuration changes are made by the Machine Config Operator (MCO), {op-system-first} must reboot for the changes to take effect. Whether the configuration change is automatic, such as when a `kube-apiserver-to-kubelet-signer` certificate authority (CA) is rotated, or manual, an {op-system} node reboots automatically unless it is paused.
 
@@ -15,7 +15,7 @@ The following modifications do not trigger a node reboot:
 * changes to the global pull secret or pull secret in the `openshift-config` namespace
 * changes to the `/etc/containers/registries.conf` file, such as adding or editing an `ImageContentSourcePolicy` object
 
-When the MCO detects any of these changes, it drains the corresponding nodes, applies the changes, and uncordons the nodes. 
+When the MCO detects any of these changes, it drains the corresponding nodes, applies the changes, and uncordons the nodes.
 ====
 
 To avoid unwanted disruptions, you can modify the machine config pool to prevent automatic rebooting after the Operator makes changes to the machine config.
@@ -62,7 +62,7 @@ Pausing a machine config pool stops all system reboot processes and all configur
 # oc get machineconfigpool/worker --template='{{.spec.paused}}'
 ----
 +
-The `spec.paused` field is `true` and the the machine config pool is paused.
+The `spec.paused` field is `true` and the machine config pool is paused.
 
 . Alternatively, to unpause the autoreboot process:
 
@@ -99,7 +99,7 @@ By unpausing a machine config pool, all paused changes are applied at reboot.
 # oc get machineconfigpool/worker --template='{{.spec.paused}}'
 ----
 +
-The `spec.paused` field is `false` and the the machine config pool is unpaused.
+The `spec.paused` field is `false` and the machine config pool is unpaused.
 
 . To see if the machine config pool has pending changes:
 +
diff --git a/modules/virt-importing-vm-datavolume.adoc b/modules/virt-importing-vm-datavolume.adoc
@@ -5,7 +5,7 @@
 [id="virt-importing-vm-datavolume_{context}"]
 = Importing a virtual machine image into a persistent volume claim by using a data volume
 
-You can import a virtual machine image into a persistent volume claim (PVC) by using a data volume. 
+You can import a virtual machine image into a persistent volume claim (PVC) by using a data volume.
 
 The virtual machine image can be hosted at an HTTP or HTTPS endpoint, or the image can be built into a container disk and stored in a container registry.
 
@@ -75,11 +75,11 @@ spec:
             storage: 10Gi
         storageClassName: local
       source:
-        http: <1> 
+        http: <1>
           url: "https://download.fedoraproject.org/pub/fedora/linux/releases/33/Cloud/x86_64/images/Fedora-Cloud-Base-33-1.2.x86_64.qcow2" <2>
           secretRef: "" <3>
           certConfigMap: "" <4>
-    status: {}	
+    status: {}
   running: true
   template:
     metadata:
@@ -105,7 +105,7 @@ spec:
         name: datavolumedisk1
 status: {}
 ----
-<1> The source type to import the image from. This example uses a HTTP endpoint. To import a container disk from a registry, replace `http` with `registry`.
+<1> The source type to import the image from. This example uses an HTTP endpoint. To import a container disk from a registry, replace `http` with `registry`.
 <2> The source of the virtual machine image you want to import. This example references a virtual machine image at an HTTP endpoint. An example of a container registry endpoint is `url: "docker://kubevirt/fedora-cloud-container-disk-demo:latest"`.
 <3> The `secretRef` parameter is optional.
 <4> The `certConfigMap` is required for communicating with servers that use self-signed certificates or certificates not signed by the system CA bundle. The referenced config map must be in the same namespace as the data volume.
diff --git a/post_installation_configuration/machine-configuration-tasks.adoc b/post_installation_configuration/machine-configuration-tasks.adoc
@@ -27,14 +27,14 @@ include::modules/checking-mco-status.adoc[leveloffset=+2]
 
 [id="using-machineconfigs-to-change-machines"]
 == Using MachineConfigs to configure nodes
-Tasks in this section let you create MachineConfig objects to modify files, systemd unit files, and other operating system features running on {product-title} nodes. For more ideas on working with MachineConfigs, see 
+Tasks in this section let you create MachineConfig objects to modify files, systemd unit files, and other operating system features running on {product-title} nodes. For more ideas on working with MachineConfigs, see
  content related to link:https://access.redhat.com/solutions/5307301[changing MTU network settings], link:https://access.redhat.com/solutions/5096731[adding] or
-link:https://access.redhat.com/solutions/4510281[updating] SSH authorized keys, , link:https://access.redhat.com/solutions/4518671[replacing DNS nameservers], link:https://access.redhat.com/verify-images-ocp4[verifying image signatures], link:https://access.redhat.com/solutions/4727321[enabling SCTP], and link:https://access.redhat.com/solutions/5170251[configuring iSCSI initiatornames] for {product-title}.
+link:https://access.redhat.com/solutions/4510281[updating] SSH authorized keys, link:https://access.redhat.com/solutions/4518671[replacing DNS nameservers], link:https://access.redhat.com/verify-images-ocp4[verifying image signatures], link:https://access.redhat.com/solutions/4727321[enabling SCTP], and link:https://access.redhat.com/solutions/5170251[configuring iSCSI initiatornames] for {product-title}.
 
-MachineConfigs 
+MachineConfigs
 
 {product-title} version 4.6 supports
-link:https://github.com/coreos/ignition/blob/master/docs/configuration-v3_1.md[Ignition specification version 3.1]. 
+link:https://github.com/coreos/ignition/blob/master/docs/configuration-v3_1.md[Ignition specification version 3.1].
 All new MachineConfigs you create going forward should be based on
 Ignition specification version 3.1.  If you are upgrading your {product-title} cluster,
 any existing Ignition specification version 2.x MachineConfigs will be translated automatically to

Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,7 @@ An index pattern defines the Elasticsearch indices that you want to visualize. T`
`11`	`11`
`12`	`12`	* A user must have the `cluster-admin` role, the `cluster-reader` role, or both roles to view the infra and audit indices in Kibana. The default `kubeadmin` user has proper permissions to view these indices.
`13`	`13`	`+`
`14`		-If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access the these indices. You can use the following command to check if the current user has appropriate permissions:
	`14`	+If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access these indices. You can use the following command to check if the current user has appropriate permissions:
`15`	`15`	`+`
`16`	`16`	`[source,terminal]`
`17`	`17`	`----`
Original file line number	Diff line number	Diff line change
`@@ -13,9 +13,9 @@ You view cluster logs in the Kibana web console. The methods for viewing and vis`
`13`	`13`
`14`	`14`	`* Kibana index patterns must exist.`
`15`	`15`
`16`		-* A user must have the `cluster-admin` role, the `cluster-reader` role, or both roles to view the infra and audit indices in Kibana. The default `kubeadmin` user has proper permissions to view these indices.
	`16`	+* A user must have the `cluster-admin` role, the `cluster-reader` role, or both roles to view the infra and audit indices in Kibana. The default `kubeadmin` user has proper permissions to view these indices.
`17`	`17`	`+`
`18`		-If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access the these indices. You can use the following command to check if the current user has appropriate permissions:
	`18`	+If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access these indices. You can use the following command to check if the current user has appropriate permissions:
`19`	`19`	`+`
`20`	`20`	`[source,terminal]`
`21`	`21`	`----`
Original file line number	Diff line number	Diff line change
`@@ -10,9 +10,9 @@ pie charts, heat maps, built-in geospatial support, and other visualizations.`
`10`	`10`
`11`	`11`	`.Prerequisites`
`12`	`12`
`13`		-* To list the infra and audit indices in Kibana, a user must have the `cluster-admin` role, the `cluster-reader` role, or both roles. The default `kubeadmin` user has proper permissions to list these indices.
	`13`	+* To list the infra and audit indices in Kibana, a user must have the `cluster-admin` role, the `cluster-reader` role, or both roles. The default `kubeadmin` user has proper permissions to list these indices.
`14`	`14`	`+`
`15`		-If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access the these indices. You can use the following command to check if the current user has proper permissions:
	`15`	+If you can view the pods and logs in the `default`, `kube-` and `openshift-` projects, you should be able to access these indices. You can use the following command to check if the current user has proper permissions:
`16`	`16`	`+`
`17`	`17`	`[source,terminal]`
`18`	`18`	`----`
`@@ -44,4 +44,3 @@ The Kibana interface launches.`
`44`	`44`	`====`
`45`	`45`	`If you get a security_exception error in the Kibana console and cannot access your Kibana indices, you might have an expired OAuth token. If you see this error, log out of the Kibana console, and then log back in. This refreshes your OAuth tokens and you should be able to access your indices.`
`46`	`46`	`====`
`47`		`-`
Original file line number	Diff line number	Diff line change
`@@ -89,7 +89,7 @@ For example:`
`89`	`89`	`$ oc patch Scheduler cluster --type='merge' -p '{"spec":{"policy":{"name":"scheduler-policy"}}}' --type=merge`
`90`	`90`	`----`
`91`	`91`	`+`
`92`		-After making the change to the `Scheduler` config resource, wait for the `opensift-kube-apiserver` pods to redeploy. This can take several minutes. Until the pods redeploy, new scheduler does not take effect.
	`92`	+After making the change to the `Scheduler` config resource, wait for the `openshift-kube-apiserver` pods to redeploy. This can take several minutes. Until the pods redeploy, new scheduler does not take effect.
`93`	`93`
`94`	`94`	. Verify the scheduler policy is configured by viewing the log of a scheduler pod in the `openshift-kube-scheduler` namespace. The following command checks for the predicates and priorities that are being registered by the scheduler:
`95`	`95`	`+`