Merge pull request #79259 from sheriff-rh/OCPBUGS-29730

Author: sheriff-rh

modules/available-persistent-storage-options.adoc

@@ -20,7 +20,7 @@ a|* Presented to the operating system (OS) as a block device
 bypassing the file system
 * Also referred to as a Storage Area Network (SAN)
 * Non-shareable, which means that only one client at a time can mount an endpoint of this type
-| AWS EBS and VMware vSphere support dynamic persistent volume (PV) provisioning natively in {product-title}.
+| AWS EBS and VMware vSphere support dynamic persistent volume (PV) provisioning natively in the {product-title}.
 // Ceph RBD, OpenStack Cinder, Azure Disk, GCE persistent disk
 
 |File

modules/configuring-haproxy-interval.adoc

@@ -6,7 +6,7 @@
 [id="configuring-haproxy-interval_{context}"]
 = Configuring HAProxy reload interval
 
-When you update a route or an endpoint associated with a route, {product-title} router updates the configuration for HAProxy. Then, HAProxy reloads the updated configuration for those changes to take effect. When HAProxy reloads, it generates a new process that handles new connections using the updated configuration.
+When you update a route or an endpoint associated with a route, the {product-title} router updates the configuration for HAProxy. Then, HAProxy reloads the updated configuration for those changes to take effect. When HAProxy reloads, it generates a new process that handles new connections using the updated configuration.
 
 HAProxy keeps the old process running to handle existing connections until those connections are all closed. When old processes have long-lived connections, these processes can accumulate and consume resources.
 

modules/recommended-configurable-storage-technology.adoc

@@ -80,9 +80,9 @@ A scaled registry is an {product-registry} where two or more pod replicas are ru
 
 [IMPORTANT]
 ====
-Testing shows issues with using the NFS server on {op-system-base-full} as storage backend for core services. This includes the OpenShift Container Registry and Quay, Prometheus for monitoring storage, and Elasticsearch for logging storage. Therefore, using {op-system-base} NFS to back PVs used by core services is not recommended.
+Testing shows issues with using the NFS server on {op-system-base-full} as a storage backend for core services. This includes the OpenShift Container Registry and Quay, Prometheus for monitoring storage, and Elasticsearch for logging storage. Therefore, using {op-system-base} NFS to back PVs used by core services is not recommended.
 
-Other NFS implementations on the marketplace might not have these issues. Contact the individual NFS implementation vendor for more information on any testing that was possibly completed against these {product-title} core components.
+Other NFS implementations in the marketplace might not have these issues. Contact the individual NFS implementation vendor for more information on any testing that was possibly completed against these {product-title} core components.
 ====
 
 === Registry