Removes ipv6 unsupported note from Operator docs (quay#1122)

Co-authored-by: Steven Smith <[email protected]>

Author: stevsmit

modules/operator-ipv6-dual-stack.adoc

@@ -18,7 +18,7 @@ Use the following procedure to enable IPv6 support on your {productname} deploym
 
 .Prerequisites 
 
-* You have updated {productname} to 3.8.
+* You have updated {productname} to at least version 3.8.
 * Your host and container software platform (Docker, Podman) must be configured to support IPv6. 
 
 .Procedure 
@@ -27,13 +27,13 @@ Use the following procedure to enable IPv6 support on your {productname} deploym
 +
 [source,yaml]
 ----
----
+# ...
 FEATURE_GOOGLE_LOGIN: false
 FEATURE_INVITE_ONLY_USER_CREATION: false
 FEATURE_LISTEN_IP_VERSION: IPv6
 FEATURE_MAILING: false
 FEATURE_NONSUPERUSER_TEAM_SYNCING_SETUP: false
----
+# ...
 ----
 
 . Start, or restart, your {productname} deployment. 
@@ -62,6 +62,4 @@ For more information, see link:https://issues.redhat.com/browse/PROJQUAY-4433[PR
 
 * Currently, attempting to configure your {productname} deployment with Amazon S3 CloudFront will not work on IPv6 single stack environments. Because the endpoint of Amazon S3 CloudFront does not support IPv6, there is no workaround in place for this issue. 
 +
-For more information, see link:https://issues.redhat.com/browse/PROJQUAY-4470[PROJQUAY-4470]. 
-
-* Currently, dual-stack (IPv4 and IPv6) support does not work on {productname} {ocp} deployments. When {productname} 3.8 is deployed on {ocp} with dual-stack support enabled, the Quay Route generated by the {productname} Operator only generates an IPv4 address, and not an IPv6 address. As a result, clients with an IPv6 address cannot access the {productname} application on {ocp}. This limitation is scheduled to be fixed in a future version of {ocp}. 
+For more information, see link:https://issues.redhat.com/browse/PROJQUAY-4470[PROJQUAY-4470].