diff --git a/content/en/blog/_posts/2021-12-07-dual-stack-networking-ga.md b/content/en/blog/_posts/2021-12-08-dual-stack-networking-ga.md
similarity index 81%
rename from content/en/blog/_posts/2021-12-07-dual-stack-networking-ga.md
rename to content/en/blog/_posts/2021-12-08-dual-stack-networking-ga.md
index bab55f5fef083..a46faf5ac744c 100644
--- a/content/en/blog/_posts/2021-12-07-dual-stack-networking-ga.md
+++ b/content/en/blog/_posts/2021-12-08-dual-stack-networking-ga.md
@@ -1,7 +1,7 @@
 ---
 layout: blog
 title: 'Kubernetes 1.23: Dual-stack IPv4/IPv6 Networking Reaches GA'
-date: 2021-12-07
+date: 2021-12-08
 slug: dual-stack-networking-ga
 ---
 
@@ -24,9 +24,14 @@ The Service API now has new fields to support dual-stack, replacing the single i
 
 ## Default behavior remains single-stack
 
-Starting in 1.20, the underlying networking for Kubernetes has included dual-stack whether or not a cluster was configured with the feature flag to enable dual-stack. Now that the feature is stable in 1.23, the feature flag is removed.
 
-However, Pods and Services default to single-stack unless `ipFamilyPolicy` specifies PreferDualStack or RequireDualStack. Even though dual-stack is possible, it is not mandatory to use it. Examples in the documentation show the variety possible in [dual-stack service configuration](/docs/concepts/services-networking/dual-stack/#dual-stack-service-configuration-scenarios).
+Starting in 1.20 with the re-implementation of dual-stack services as alpha, the underlying networking for Kubernetes has included dual-stack whether or not a cluster was configured with the feature flag to enable dual-stack.
+
+Kubernetes 1.23 removed that feature flag as part of graduating the feature to stable. Dual-stack networking is always available if you want to configure it. You can set your cluster network to operate as single-stack IPv4, as single-stack IPv6, or as dual-stack IPv4/IPv6.
+
+Pods and Services default to whatever the CNI plugin sets. If your CNI plugin assigns single-stack IPs, you will have single-stack unless `ipFamilyPolicy` specifies PreferDualStack or RequireDualStack. If your CNI plugin assigns dual-stack IPs, `pod.status.PodIPs` defaults to dual-stack.
+
+Even though dual-stack is possible, it is not mandatory to use it. Examples in the documentation show the variety possible in [dual-stack service configuration](/docs/concepts/services-networking/dual-stack/#dual-stack-service-configuration-scenarios).
 
 
 ## Try dual-stack right now