diff --git a/content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md b/content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
index 7bc86ee9b21fa..54d5e07b87a52 100644
--- a/content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
+++ b/content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
@@ -5,11 +5,11 @@ date: 2023-11-13
 slug: pod-ready-to-start-containers-condition-now-in-beta
 ---
 
-**Author**: Kevin Hannon(Red Hat)  zefeng chen
+**Author**: zefeng chen, Kevin Hannon(Red Hat)
 
 
-With Kubernetes 1.29 the PodReadyToStartContainersCondition functionality entered beta and is available by default.
-A new kubelet-managed pod condition in the status field of a pod. The kubelet will use the PodHasNetwork condition to accurately surface the initialization state of a pod,
+With recent release of Kubernetes 1.29 the `PodReadyToStartContainers`[condition](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions) is available by default.
+The kubelet manages the value for that condition throughout a Pod's lifecycle, in the status field of a pod. The kubelet will use the PodReadyToStartContainers condition to accurately surface the initialization state of a pod,
 From the perspective of pod sandbox creation and network configuration by a container runtime
 
 ## Some history