Merge pull request #87546 from skopacz1/OSDOCS-12533_2

OSDOCS-12533: OCI GA follow up

Author: skopacz1

modules/abi-oci-resources-services.adoc

@@ -18,7 +18,7 @@ To ensure compatibility with {product-title}, you must set `A` as the record typ
 * `api-int.<cluster_name>.<base_domain>`, which targets the `apiVIP` parameter of the API load balancer.
 * `*.apps.<cluster_name>.<base_domain>`, which targets the `ingressVIP` parameter of the Ingress load balancer.
 
-The `api.+*+` and `api-int.+*+` DNS records relate to control plane machines, so you must ensure that all nodes in your installed {product-title} cluster can access these DNS records.
+The `api.{asterisk}` and `api-int.{asterisk}` DNS records relate to control plane machines, so you must ensure that all nodes in your installed {product-title} cluster can access these DNS records.
 ====
 
 .Prerequisites
@@ -27,4 +27,8 @@ The `api.+*+` and `api-int.+*+` DNS records relate to control plane machines, so
 
 .Procedure
 
-* Create the required {oci} resources and services. See link:https://docs.oracle.com/iaas/Content/openshift-on-oci/agent-prereq.htm[{oci} Resources Needed for Using the Agent-based Installer (Oracle documentation)].
+* Create the required {oci} resources and services.
++
+For installations in a connected environment, see link:https://docs.oracle.com/en-us/iaas/Content/openshift-on-oci/agent-installer-using-stack.htm[Provisioning Cluster Infrastructure Using Terraform (Oracle documentation)].
++
+For installations in a disconnected environment, see link:https://docs.oracle.com/iaas/Content/openshift-on-oci/agent-prereq.htm[Provisioning OCI Resources for the Agent-based Installer in Disconnected Environments (Oracle documentation)].

modules/installing-oci-about-agent-based-installer.adoc

@@ -20,7 +20,7 @@ image::684_OpenShift_Installing_on_OCI_0624-connected.png[Image of a high-level
 .Workflow for using the Agent-based installer in a disconnected environment to install a cluster on {oci}
 image::684_OpenShift_Installing_on_OCI_0624-disconnected.png[Image of a high-level workflow for using the Agent-based installer in a disconnected environment to install a cluster on {oci}]
 
-{oci} provides services that can meet your regulatory compliance, performance, and cost-effectiveness needs. {oci} supports 64-bit `x86` instances and 64-bit `ARM` instances. Additionally, {oci} provides an {ocvs} service where you can move VMware workloads to {oci} with minimal application re-architecture.
+{oci} provides services that can meet your regulatory compliance, performance, and cost-effectiveness needs. {oci} supports 64-bit `x86` instances and 64-bit `ARM` instances.
 
 [NOTE]
 ====
@@ -33,10 +33,6 @@ By running your {product-title} cluster on {oci}, you can access the following c
 
 * Block Volume storage, where you can configure scaling and auto-tuning settings for your storage volume, so that the Block Volume service automatically adjusts the performance level to optimize performance.
 
-// Should I remove the reference below of ocvs? If so, what should the new phrasing be?
-
-* {ocvs-first}, where you can deploy a cluster in a public-cloud environment that operates on a VMware® vSphere software-defined data center (SDDC). You continue to retain full-administrative control over your VMware vSphere environment, but you can use {oci} services to improve your applications on flexible, scalable, and secure infrastructure.
-
 [IMPORTANT]
 ====
 To ensure the best performance conditions for your cluster workloads that operate on {oci} and on the OCVS service, ensure volume performance units (VPUs) for your block volume is sized for your workloads. The following list provides some guidance in selecting the VPUs needed for specific performance needs: