Merge pull request #28346 from brian-avery/fixGrammarIssuesWithOpenShiftDocs

vikram-redhat · web-flow · commit 91ecf22325af · 2021-01-06T19:29:25.000+10:00
Spelling and Grammar fixes
diff --git a/modules/cluster-logging-cpu-memory.adoc b/modules/cluster-logging-cpu-memory.adoc
@@ -80,6 +80,6 @@ spec:
             memory: 736Mi
 ----
 <1> Specify the CPU and memory limits and requests for the log store as needed. For Elasticsearch, you must adjust both the request value and the limit value.
-<2> Specify the CPU and memory limits and requests for the log visualizater as needed.
+<2> Specify the CPU and memory limits and requests for the log visualizer as needed.
 <3> Specify the CPU and memory limits and requests for the log curator as needed.
 <4> Specify the CPU and memory limits and requests for the log collector as needed.
diff --git a/modules/cluster-logging-elasticsearch-rules.adoc b/modules/cluster-logging-elasticsearch-rules.adoc
@@ -15,7 +15,7 @@ You can view these alerting rules in Prometheus.
 
 
 |ElasticsearchClusterNotHealthy
-|The cluster health status has been RED for at least 2 minutes. The cluster does not accept writes, shards may be missing, or themaster
+|The cluster health status has been RED for at least 2 minutes. The cluster does not accept writes, shards may be missing, or the master
  node hasn't been elected yet.
 |critical
 
diff --git a/modules/cnf-configuring-huge-pages.adoc b/modules/cnf-configuring-huge-pages.adoc
@@ -7,7 +7,7 @@
 
 Nodes must pre-allocate huge pages used in an {product-title} cluster. Use the Performance Addon Operator to allocate huge pages on a specific node.
 
-{product-title} provides a method for creating and allocating huge pages. Performance Addon Operator provides an easier method for doing  thisusing the performance profile.
+{product-title} provides a method for creating and allocating huge pages. Performance Addon Operator provides an easier method for doing  this using the performance profile.
 
 For example, in the `hugepages` `pages` section of the performance profile, you can specify multiple blocks of `size`, `count`, and, optionally, `node`:
 
diff --git a/modules/images-configuration-allowed.adoc b/modules/images-configuration-allowed.adoc
@@ -6,7 +6,7 @@
 [id="images-configuration-allowed_{context}"]
 = Adding specific registries
 
-You can add a list of registries that are permitted for image pull and push actions by by editing the `image.config.openshift.io/cluster` custom resource (CR). {product-title} applies the changes to this CR to all nodes in the cluster. 
+You can add a list of registries that are permitted for image pull and push actions by editing the `image.config.openshift.io/cluster` custom resource (CR). {product-title} applies the changes to this CR to all nodes in the cluster. 
 
 When pulling or pushing images, the container runtime searches the registries listed under the `registrySources` parameter in the `image.config.openshift.io/cluster` CR. If you created a list of registries under the `allowedRegistries` parameter, the container runtime searches only those registries. Registries not in the list are blocked.
 
diff --git a/modules/installation-creating-azure-control-plane.adoc b/modules/installation-creating-azure-control-plane.adoc
@@ -21,7 +21,7 @@ contact Red Hat support with your installation logs.
 
 * Configure an Azure account.
 * Generate the Ignition config files for your cluster.
-* Create and configure a VNet and assoicated subnets in Azure.
+* Create and configure a VNet and associated subnets in Azure.
 * Create and configure networking and load balancers in Azure.
 * Create control plane and compute roles.
 * Create the bootstrap machine.
diff --git a/modules/installation-deployment-manager-control-plane.adoc b/modules/installation-deployment-manager-control-plane.adoc
@@ -6,7 +6,7 @@
 [id="installation-deployment-manager-control-plane_{context}"]
 = Deployment Manager template for control plane machines
 
-You can use the following Deployment Mananger template to deploy the control
+You can use the following Deployment Manager template to deploy the control
 plane machines that you need for your {product-title} cluster:
 
 .`05_control_plane.py` Deployment Manager template
diff --git a/modules/installation-infrastructure-user-infra.adoc b/modules/installation-infrastructure-user-infra.adoc
@@ -16,7 +16,7 @@ endif::[]
 Before you deploy an {product-title} cluster that uses user-provisioned
 infrastructure, you must create the underlying infrastructure.
 
-.Prerequistes
+.Prerequisites
 
 * Review the link:https://access.redhat.com/articles/4128421[{product-title} 4.x Tested Integrations]
 page before you create the supporting infrastructure for your cluster.
diff --git a/modules/installation-rhv-making-control-plane-nodes-non-schedulable.adoc b/modules/installation-rhv-making-control-plane-nodes-non-schedulable.adoc
@@ -12,7 +12,7 @@
 //
 // "NOTE: Router pods can run also on control-plane nodes but there are some Kubernetes limitations that prevent the ingress load balancer from reaching those pods.""
 
-Because you are are manually creating and deploying the control plane machines, you must configure a manifest file to make the control plane nodes non-schedulable.
+Because you are manually creating and deploying the control plane machines, you must configure a manifest file to make the control plane nodes non-schedulable.
 
 .Procedure
 
diff --git a/modules/installing-wmco-using-web-console.adoc b/modules/installing-wmco-using-web-console.adoc
@@ -9,7 +9,7 @@ You can use the {product-title} web console to install the Windows Machine Confi
 
 .Procedure
 
-. From the *Adminstrator* perspective in the {product-title} web console, navigate to the *Operators -> OperatorHub* page.
+. From the *Administrator* perspective in the {product-title} web console, navigate to the *Operators -> OperatorHub* page.
 
 . Use the *Filter by keyword* box to search for `Windows Machine Config Operator` in the catalog. Click the *Windows Machine Config Operator* tile.
 
diff --git a/modules/monitoring-configuring-alert-receivers.adoc b/modules/monitoring-configuring-alert-receivers.adoc
@@ -61,7 +61,7 @@ Alternatively, you can navigate to the same page through the notification drawer
 . By default, firing alerts with labels that match all of the selectors will be sent to the receiver. If you want label values for firing alerts to be matched exactly before they are sent to the receiver:
 .. Add routing label names and values in the *Routing Labels* section of the form.
 +
-.. Select *Regular Expression* if want to to use a regular expression.
+.. Select *Regular Expression* if want to use a regular expression.
 +
 .. Select *Add Label* to add further routing labels.
 
diff --git a/modules/monitoring-querying-metrics-for-user-defined-projects-as-a-developer.adoc b/modules/monitoring-querying-metrics-for-user-defined-projects-as-a-developer.adoc
@@ -11,7 +11,7 @@ In the *Developer* perspective, the Metrics UI includes some predefined CPU, mem
 
 [NOTE]
 ====
-Developers can only use the *Developer* perspective and not the *Administrator* perspective. As a developer you can can only query metrics for one project at a time. Developers cannot access the third-party UIs provided with {product-title} monitoring.
+Developers can only use the *Developer* perspective and not the *Administrator* perspective. As a developer you can only query metrics for one project at a time. Developers cannot access the third-party UIs provided with {product-title} monitoring.
 ====
 
 .Prerequisites
diff --git a/modules/olm-package-manifest-format-catalogsource.adoc b/modules/olm-package-manifest-format-catalogsource.adoc
@@ -90,4 +90,4 @@ NAME    CATALOG              AGE
 etcd    My Operator Catalog  34s
 ----
 
-You can now install the Operators from your customer catalog by using the the *OperatorHub* page on your {product-title} cluster web console.
+You can now install the Operators from your customer catalog by using the *OperatorHub* page on your {product-title} cluster web console.
diff --git a/modules/serverless-kafka-source-odc.adoc b/modules/serverless-kafka-source-odc.adoc
@@ -27,7 +27,7 @@ You can create and verify a Kafka event source from the {product-title} web cons
 .. Enter a *Name* for the Kafka event source.
 . Click *Create*.
 
-.Verfication steps
+.Verification steps
 
 You can verify that the Kafka event source was created and is connected to the sink by viewing the *Topology* page.
 
diff --git a/modules/serverless-pingsource-kn.adoc b/modules/serverless-pingsource-kn.adoc
@@ -64,7 +64,7 @@ Conditions:
   ++ ResourcesCorrect     15s
 ----
 
-.Verfication steps
+.Verification steps
 
 You can verify that the Kubernetes events were sent to the Knative event sink by looking at the sink pod's logs.
 
diff --git a/modules/serverless-pingsource-odc.adoc b/modules/serverless-pingsource-odc.adoc
@@ -46,7 +46,7 @@ spec:
 .. Select a *Sink*. This can be either a *Resource* or a *URI*. In this example, the `event-display` service created in the previous step is used as the *Resource* sink.
 .. Click *Create*.
 
-.Verfication steps
+.Verification steps
 
 You can verify that the PingSource was created and is connected to the sink by viewing the *Topology* page.
 
diff --git a/modules/serverless-pingsource-yaml.adoc b/modules/serverless-pingsource-yaml.adoc
@@ -112,7 +112,7 @@ spec:
       namespace: default
 ----
 
-.Verfication steps
+.Verification steps
 
 You can verify that the Kubernetes events were sent to the Knative event sink by looking at the sink pod's logs.
 

Original file line number	Diff line number	Diff line change
`@@ -61,7 +61,7 @@ Alternatively, you can navigate to the same page through the notification drawer`
`61`	`61`	`. By default, firing alerts with labels that match all of the selectors will be sent to the receiver. If you want label values for firing alerts to be matched exactly before they are sent to the receiver:`
`62`	`62`	`.. Add routing label names and values in the Routing Labels section of the form.`
`63`	`63`	`+`
`64`		`-.. Select Regular Expression if want to to use a regular expression.`
	`64`	`+.. Select Regular Expression if want to use a regular expression.`
`65`	`65`	`+`
`66`	`66`	`.. Select Add Label to add further routing labels.`
`67`	`67`