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:

https://docs.openshift.com/container-platform/4.15/scalability_and_performance/optimization/optimizing-storage.html 

https://docs.openshift.com/container-platform/4.15/scalability_and_performance/optimization/routing-optimization.html

https://docs.openshift.com/container-platform/4.15/scalability_and_performance/optimization/optimizing-networking.html 

https://docs.openshift.com/container-platform/4.15/scalability_and_performance/optimization/optimizing-cpu-usage.html

Optimizing storage - Scalability and performance optimization

ORIGINAL: AWS EBS and VMware vSphere support dynamic persistent volume (PV) provisioning natively in OpenShift Container Platform.

SUGGESTION: AWS EBS and VMware vSphere support dynamic persistent volume (PV) provisioning natively in the OpenShift Container Platform.

ORIGINAL: Testing shows issues with using the NFS server on Red Hat Enterprise Linux (RHEL) as storage backend for core services. 

SUGGESTION: Testing shows issues with using the NFS server on Red Hat Enterprise Linux (RHEL) as a storage backend for core services. 

ORIGINAL: Other NFS implementations on the marketplace might not have these issues.

SUGGESTION: Other NFS implementations in the marketplace might not have these issues.

Optimizing routing - Scalability and performance optimization

ORIGINAL: Back end server page size

SUGGESTION: Back-end server page size

ORIGINAL:  When you update a route or an endpoint associated with a route, OpenShift Container Platform router updates the configuration for HAProxy. 

SUGGESTION:  When you update a route or an endpoint associated with a route, the OpenShift Container Platform router updates the configuration for HAProxy. 

Optimizing networking - Scalability and performance optimization

ORIGINAL: Because encrypting and decrypting node hosts uses CPU power, performance is affected both in throughput and CPU usage on the nodes when encryption is enabled, regardless of the IP security system being used.

SUGGESTION: Because encrypting and decrypting node hosts use CPU power, performance is affected both in throughput and CPU usage on the nodes when encryption is enabled, regardless of the IP security system being used.

Optimizing CPU usage with mount namespace encapsulation

ORIGINAL: Both scenarios show example containers which have mount propagation settings of bidirectional, host-to-container, and none.

SUGGESTION: Both scenarios show example containers that have mount propagation settings of bidirectional, host-to-container, and none.