Merge pull request #67093 from aireilly/fix-postinstallation

Typos: Fix incorrect hyphenation per ISG

Author: kelbrown20

.vale/styles/Vocab/OpenShiftDocs/accept.txt

@@ -13,3 +13,5 @@ Mbps
 MetalLB
 Operator
 Operators
+[Pp]reinstall
+[Pp]ostinstall

cloud_experts_tutorials/cloud-experts-entra-id-idp.adoc

@@ -163,7 +163,7 @@ Once the cluster authentication Operator reconciles your changes (generally with
 
 Once you log in, you will notice that you have very limited permissions. This is because, by default, OpenShift only grants you the ability to create new projects (namespaces) in the cluster. Other projects (namespaces) are restricted from view.
 
-OpenShift includes a significant number of pre-configured roles, including the `cluster-admin` role that grants full access and control over the cluster. To grant your user access to the `cluster-admin` role, run the following command:
+OpenShift includes a significant number of preconfigured roles, including the `cluster-admin` role that grants full access and control over the cluster. To grant your user access to the `cluster-admin` role, run the following command:
 
 [source,terminal]
 ----
@@ -180,7 +180,7 @@ $ rosa grant user cluster-admin \
 
 If you opted to enable group claims, the cluster OAuth provider will automatically create or update the membership of groups the user is a member of (using the group ID). The cluster OAuth provider **does not** automatically create RoleBindings and ClusterRoleBindings for the groups that are created, you are responsible for creating those via your own processes.
 
-OpenShift includes a significant number of pre-configured roles, including the `cluster-admin` role that grants full access and control over the cluster. To grant an automatically generated group access to the `cluster-admin` role, you must create a ClusterRoleBinding to the group ID.
+OpenShift includes a significant number of preconfigured roles, including the `cluster-admin` role that grants full access and control over the cluster. To grant an automatically generated group access to the `cluster-admin` role, you must create a ClusterRoleBinding to the group ID.
 
 [source,terminal]
 ----

installing/installing-preparing.adoc

@@ -103,7 +103,7 @@ You can use the assisted installer to deploy xref:../installing/installing_sno/i
 == Preparing your cluster for users after installation
 
 Some configuration is not required to install the cluster but recommended before your users access the cluster. You can customize the cluster itself by xref:../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[customizing] the Operators that make up your cluster and integrate you cluster with other required systems, such as an identity provider.
-//This link will change when we consolidate the customizations page with the post-installation activities.
+//This link will change when we consolidate the customizations page with the postinstallation activities.
 
 For a production cluster, you must configure the following integrations:
 

installing/installing_bare_metal_ipi/ipi-install-post-installation-configuration.adoc

@@ -1,15 +1,15 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="ipi-install-post-installation-configuration"]
-= Installer-provisioned post-installation configuration
+= Installer-provisioned postinstallation configuration
 include::_attributes/common-attributes.adoc[]
 :context: ipi-install-post-installation-configuration
 
 toc::[]
 
-After successfully deploying an installer-provisioned cluster, consider the following post-installation procedures.
+After successfully deploying an installer-provisioned cluster, consider the following postinstallation procedures.
 
 include::modules/ipi-install-configuring-ntp-for-disconnected-clusters.adoc[leveloffset=+1]
 
 include::modules/nw-enabling-a-provisioning-network-after-installation.adoc[leveloffset=+1]
 
-include::modules/nw-osp-configuring-external-load-balancer.adoc[leveloffset=+1]
+include::modules/nw-osp-configuring-external-load-balancer.adoc[leveloffset=+1]

installing/installing_openstack/installing-openstack-nfv-preparing.adoc

@@ -28,7 +28,7 @@ You must configure {rh-openstack} before you install a cluster that uses SR-IOV
 
 * Complete link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/network_functions_virtualization_planning_and_configuration_guide/part-dpdk-configure#p-ovs-dpdk-flavor-deploy-instance[Creating a flavor and deploying an instance for OVS-DPDK] before you install a cluster on {rh-openstack}.
 
-After you perform pre-installation tasks, install your cluster by following the most relevant {product-title} on {rh-openstack} installation instructions. Then, perform the tasks under "Next steps" on this page.
+After you perform preinstallation tasks, install your cluster by following the most relevant {product-title} on {rh-openstack} installation instructions. Then, perform the tasks under "Next steps" on this page.
 
 [id="next-steps_installing-openstack-nfv-preparing"]
 == Next steps

installing/installing_vsphere/preparing-to-install-on-vsphere.adoc

@@ -36,7 +36,7 @@ The steps for performing a user-provisioned infrastructure installation are prov
 
 === Installer-provisioned infrastructure installation of {product-title} on vSphere
 
-Installer-provisioned infrastructure allows the installation program to pre-configure and automate the provisioning of resources required by {product-title}.
+Installer-provisioned infrastructure allows the installation program to preconfigure and automate the provisioning of resources required by {product-title}.
 
 * **xref:../../installing/installing_vsphere/installing-vsphere-installer-provisioned.adoc#installing-vsphere-installer-provisioned[Installing a cluster on vSphere]**: You can install {product-title} on vSphere by using installer-provisioned infrastructure installation with no customization.
 

logging/cluster-logging-deploying.adoc

@@ -41,7 +41,7 @@ ifdef::openshift-rosa,openshift-dedicated[]
 * link:https://docs.openshift.com/container-platform/latest/logging/config/cluster-logging-log-store.html#cluster-logging-removing-unused-components-if-no-elasticsearch_cluster-logging-log-store[Removing unused components if you do not use the default Elasticsearch log store]
 endif::[]
 
-== Post-installation tasks
+== Postinstallation tasks
 
 If you plan to use Kibana, you must xref:#cluster-logging-visualizer-indices_cluster-logging-deploying[manually create your Kibana index patterns and visualizations] to explore and visualize data in Kibana.
 
@@ -50,7 +50,7 @@ If your network plugin enforces network isolation, xref:#cluster-logging-deploy-
 
 include::modules/cluster-logging-deploy-cli.adoc[leveloffset=+1]
 
-== Post-installation tasks
+== Postinstallation tasks
 
 If you plan to use Kibana, you must xref:#cluster-logging-visualizer-indices_cluster-logging-deploying[manually create your Kibana index patterns and visualizations] to explore and visualize data in Kibana.
 

machine_management/user_infra/adding-compute-user-infra-general.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-You can add compute machines to a cluster on user-provisioned infrastructure either as part of the installation process or after installation. The post-installation process requires some of the same configuration files and parameters that were used during installation.
+You can add compute machines to a cluster on user-provisioned infrastructure either as part of the installation process or after installation. The postinstallation process requires some of the same configuration files and parameters that were used during installation.
 
 [id="upi-adding-compute-aws"]
 == Adding compute machines to Amazon Web Services

metering/configuring_metering/metering-configure-aws-billing-correlation.adoc

@@ -113,4 +113,4 @@ To store data in S3, the `aws-access-key-id` and `aws-secret-access-key` credent
 ----
 <1> Replace `operator-metering-data` with the name of your bucket.
 
-This can be done either pre-installation or post-installation. Disabling it post-installation can cause errors in the Reporting Operator.
+This can be done either preinstallation or postinstallation. Disabling it postinstallation can cause errors in the Reporting Operator.

modules/assisted-installer-assisted-installer-prerequisites.adoc

@@ -48,7 +48,7 @@ The {product-title} cluster's network must also meet the following requirements:
 
 == Preflight validations
 
-The {ai-full} ensures the cluster meets the prerequisites before installation, because it eliminates complex post-installation troubleshooting, thereby saving significant amounts of time and effort. Before installing software on the nodes, the {ai-full} conducts the following validations:
+The {ai-full} ensures the cluster meets the prerequisites before installation, because it eliminates complex postinstallation troubleshooting, thereby saving significant amounts of time and effort. Before installing software on the nodes, the {ai-full} conducts the following validations:
 
 * Ensures network connectivity
 * Ensures sufficient network bandwidth