Merge pull request #49602 from amolnar-rh/OCPBUGS-202

OCPBUGS202: Correcting ztp-site-generator instances to ztp-site-generate

Author: opayne1

modules/ztp-policygentemplates-for-ran.adoc

@@ -8,7 +8,7 @@
 
 You use `PolicyGenTemplate` custom resources (CRs) to customize the configuration applied to the cluster using the GitOps zero touoch provisioning (ZTP) pipeline. The baseline configuration, obtained from the GitOps ZTP container, is designed to provide a set of critical features and node tuning settings that ensure the cluster can support the stringent performance and resource utilization constraints typical of RAN Distributed Unit (DU) applications. Changes or omissions from the baseline configuration can affect feature availability, performance, and resource utilization. Use `PolicyGenTemplate` CRs as the basis to create a hierarchy of configuration files tailored to your specific site requirements.
 
-The baseline `PolicyGenTemplate` CRs that are defined for RAN DU cluster configuration can be extracted from the GitOps ZTP `ztp-site-generator`. See "Preparing the ZTP Git repository" for further details.
+The baseline `PolicyGenTemplate` CRs that are defined for RAN DU cluster configuration can be extracted from the GitOps ZTP `ztp-site-generate`. See "Preparing the ZTP Git repository" for further details.
 
 The `PolicyGenTemplate` CRs can be found in the `./out/argocd/example/policygentemplates` folder. The reference architecture has common, group, and site-specific configuration CRs. Each `PolicyGenTemplate` CR refers to other CRs that can be found in the `./out/source-crs` folder.
 

modules/ztp-talo-integration.adoc

@@ -35,8 +35,8 @@ The {cgu-operator} applies the configuration policies in the order specified by
 +
 Multiple CRs and policies can share the same wave number. Having fewer policies can result in faster deployments and lower CPU usage. It is a best practice to group many CRs into relatively few waves.
 
-To check the default wave value in each source CR, run the following command against the `out/source-crs` directory that is extracted from the `ztp-site-generator` container image:
-+
+To check the default wave value in each source CR, run the following command against the `out/source-crs` directory that is extracted from the `ztp-site-generate` container image:
+
 [source,terminal]
 ----
 $ grep -r "ztp-deploy-wave" out/source-crs

scalability_and_performance/ztp-deploying-disconnected.adoc

@@ -50,7 +50,7 @@ include::modules/ztp-policygentemplates-for-ran.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* For more information about extracting the `/argocd` directory from the `ztp-site-generator` container image, see xref:../scalability_and_performance/ztp-deploying-disconnected.adoc#ztp-policygentemplates-for-ran_ztp-deploying-disconnected[Preparing the ZTP Git repository].
+* For more information about extracting the `/argocd` directory from the `ztp-site-generate` container image, see xref:../scalability_and_performance/ztp-deploying-disconnected.adoc#ztp-policygentemplates-for-ran_ztp-deploying-disconnected[Preparing the ZTP Git repository].
 
 include::modules/ztp-the-policygentemplate.adoc[leveloffset=+1]