Description of problem:

Some issues in the document needs to be corrected.

Version-Release number of selected component (if applicable):

    4.15 and may need to backport to previous releases

How reproducible:

    Every time

Steps to Reproduce:

    1.Open https://docs.openshift.com/container-platform/4.15/scalability_and_performance/scaling-worker-latency-profiles.html

The change suggestions are in bold:

1. The cluster administrator need needs change only one parameter, recorded in a file, which controls four parameters affecting how supervisory processes read status and interpret the health of the cluster.

2. These parameters can use values which allow you to control the reaction of the cluster to latency issues without needing to determine the best values using manual methods.

3. If a pod on that node is on a node that has the NoExecute taint, the pod is run runs according to tolerationSeconds. If the pod node has no taint, it will be evicted in 300 seconds (default-not-ready-toleration-seconds and default-unreachable-toleration-seconds settings of the Kube API Server).

4. The Kube Controller Manager checks the statuses of Kubelet every 5 seconds *(node-monitor-grace-period)*.
The Kubernetes Controller Manager waits 40 seconds (node-monitor-grace-period) for a status update from Kubelet before considering the Kubelet unhealthy.

5. To edit the configuration of the installer, you will first firstly need to use the command openshift-install create manifests to create the default node manifest as well as other manifest YAML files