Merge pull request #95944 from openshift-cherrypick-robot/cherry-pick-95841-to-enterprise-4.16

[enterprise-4.16] OCPBUGS-55495# Adjust language to alleviate user confusion about permissions tables

Author: mburke5678

modules/installation-vsphere-installer-infra-requirements.adoc

@@ -298,7 +298,7 @@ endif::upi[]
 ====
 
 
-Additionally, the user requires some `ReadOnly` permissions, and some of the roles require permission to propogate the permissions to child objects. These settings vary depending on whether or not you install the cluster into an existing folder.
+Additionally, the user requires some `ReadOnly` permissions, and some of the roles require permission to propagate the permissions to child objects. These settings vary depending on whether or not you install the cluster into an existing folder.
 
 .Required permissions and propagation settings
 [%collapsible]
@@ -382,7 +382,7 @@ Consider creating a custom role when an account with global administrative privi
 Accounts that are not configured with the required privileges are unsupported. Installing an {product-title} cluster in a vCenter is tested against a full list of privileges as described in the "Required vCenter account privileges" section. By adhering to the full list of privileges, you can reduce the possibility of unexpected behaviors that might occur when creating a custom role with a restricted set of privileges.
 ====
 
-The following tables list the minimum permissions for a vSphere object that interacts with specific {product-title} architecture.
+The following tables specify how the required vCenter account privileges provided earlier in this document are relevant to different aspects of {product-title} architecture.
 
 ifndef::upi[]
 [id="installation-vsphere-minimum-permissions-ipi_{context}"]