Merge pull request #98827 from lahinson/osdocs-16128-hcp-dual-stack-ga

[OSDOCS-16128]: Removing TP boilerplate about dual-stack

Author: lahinson

hosted_control_planes/hcp-disconnected/hcp-deploy-dc.adoc

@@ -15,7 +15,4 @@ In the context of {hcp}, a disconnected environment is an {product-title} deploy
 
 Depending on where the pods are running, they are affected by the `ImageDigestMirrorSet` (IDMS) or `ImageContentSourcePolicy` (ICSP) that is created in the management cluster or by the `ImageContentSource` that is set in the `spec` field of the manifest for the hosted cluster. The `spec` field is translated into an IDMS object on the hosted cluster.
 
-You can deploy {hcp} in a disconnected environment on IPv4, IPv6, and dual-stack networks. IPv4 is one of the simplest network configurations to deploy {hcp} in a disconnected environment. IPv4 ranges require fewer external components than IPv6 or dual-stack setups. For {hcp} on {VirtProductName} in a disconnected environment, use either an IPv4 or a dual-stack network.
-
-:FeatureName: {hcp-capital} in a disconnected environment on a dual-stack network
-include::snippets/technology-preview.adoc[]
+You can deploy {hcp} in a disconnected environment on IPv4, IPv6, and dual-stack networks. IPv4 is one of the simplest network configurations to deploy {hcp} in a disconnected environment. IPv4 ranges require fewer external components than IPv6 or dual-stack setups. For {hcp} on {VirtProductName} in a disconnected environment, use either an IPv4 or a dual-stack network.