fixup! docs: add dualstack cluster support documentation

Author: tthvo

docs/book/src/topics/ipv6-enabled-cluster.md

@@ -202,16 +202,9 @@ spec:
       - fd02::/112
 ```
 
-## Cloud Controller Manager IPv6 Support for Self-managed Clusters
+## Cloud Controller Manager Node IP Configurations
 
-<aside class="note warning">
-<h1>Warning</h1>
-
-The AWS Cloud Controller Manager (CCM) does not currently support dualstack Load Balancers. When creating Services of type LoadBalancer in a dualstack cluster, they will be
-assigned addresses from only one IP family.
-</aside>
-
-**Node IP addresses**: You need to provide cloud-config to the CCM via a ConfigMap to set the `NodeIPFamilies` to include IPv6. This instructs the CCM to consider IPv6 in the node's network interface. If not, the CCM will only consider node's IPv4. This causes nodes to have only IPv4 and new pods with `hostNetwork: true` will only pick up the node's IPv4 address.
+You need to provide cloud-config to the CCM via a ConfigMap to set the `NodeIPFamilies` to include IPv6. This instructs the CCM to consider IPv6 in the machine network interface, if any. If not configured, the CCM will only consider the node's IPv4 address. This causes nodes to have only IPv4 and new pods with `hostNetwork: true` will only pick up the node's IPv4 address.
 
 For example, provide the following ConfigMap to `cloud-controller-manager-addon`:
 
@@ -252,6 +245,14 @@ spec:
       name: cloud-config
 ```
 
+## Cloud Controller Manager Load Balancer Limitations
+
+<aside class="note warning">
+<h1>Warning</h1>
+
+The AWS Cloud Controller Manager (CCM) does **not** currently support dualstack Load Balancers. When creating Services of type LoadBalancer in a dualstack cluster, the Load Balancers will be created with **only** IPv4.
+</aside>
+
 ## CNI IPv6 Support for Self-managed Clusters
 
 By default, no CNI plugin is installed when provisioning a self-managed cluster. You need to install your own CNI solution that supports IPv6, for example, Calico with VXLAN. You can find the guides to enable [IPv6](https://docs.tigera.io/calico/latest/networking/ipam/ipv6) and [VXLAN](https://docs.tigera.io/calico/latest/networking/configuring/vxlan-ipip) support for Calico on their official documentation.

docs/book/src/topics/secondary-load-balancer.md

@@ -37,8 +37,6 @@ spec:
 
 ## Target Group IP Address Type
 
-**Note:** The `targetGroupIPType` field is only available when using Network Load Balancers (NLB), Application Load Balancers (ALB), or Gateway Load Balancers (ELB). It **cannot** be configured when using Classic Load Balancers.
-
 The secondary load balancer supports the same `targetGroupIPType` configuration as the primary load balancer. By default, the target group IP address type is set based on the VPC configuration:
 - If the VPC has IPv6 enabled, the target group uses `ipv6`
 - Otherwise, it defaults to `ipv4`