Merge pull request #13680 from jmencak/nto-fixes

Fixes for the Node Tuning Operator in 4.0.

Author: ahardin-rh

modules/accessing-an-example-cluster-node-tuning-operator-specification.adoc

@@ -12,5 +12,5 @@ Use this process to access an example Node Tuning Operator specification.
  . Run:
 +
 ----
-$ oc get Tuned/default -o yaml
+$ oc get Tuned/default -o yaml -n openshift-cluster-node-tuning-operator
 ----

modules/custom-tuning-specification.adoc

@@ -29,7 +29,7 @@ operator's namespace. The existence of new CRs or the deletion of old CRs is
 detected by the Operator. All existing custom tuning specifications are merged
 and appropriate objects for the containerized tuned daemons are updated.
 
-*profile: data*
+*Profile data*
 
 The `profile:` section lists tuned profiles and their names.
 
@@ -58,7 +58,7 @@ profile:
 
 *Recommended profiles*
 
-The `profile:` selection logic is defined by the `recommend` section of the CR:
+The `profile:` selection logic is defined by the `recommend:` section of the CR:
 
 ----
 recommend:

modules/node-tuning-operator.adoc

@@ -6,10 +6,10 @@
 = About the Node Tuning Operator
 
 The Node Tuning Operator helps you manage node-level tuning by orchestrating the
-tuned daemon.The majority of high-performance applications require some level of
+tuned daemon. The majority of high-performance applications require some level of
 kernel tuning. The Node Tuning Operator provides a unified management interface
 to users of node-level sysctls and more flexibility to add custom tuning, which
-is currently a Technology Preview feature, specified by user needs.The Operator
+is currently a Technology Preview feature, specified by user needs. The Operator
 manages the containerized tuned daemon for {product-title} as a Kubernetes
 DaemonSet. It ensures the custom tuning specification is passed to all
 containerized tuned daemons running in the cluster in the format that the