sync volumes pod-lifecycle

Author: asa3311

content/zh-cn/docs/concepts/storage/volumes.md

@@ -2293,6 +2293,7 @@ The following container runtimes are known to support recursive read-only mounts
 
 CRI-level:
 - [containerd](https://containerd.io/), since v2.0
+- [CRI-O](https://cri-o.io/), since v1.30
 
 OCI-level:
 - [runc](https://runc.io/), since v1.1
@@ -2303,6 +2304,7 @@ OCI-level:
 CRI 级别：
 
 - [containerd](https://containerd.io/)，自 v2.0 起
+- [CRI-O](https://cri-o.io/)，自 v1.30 起
 
 OCI 级别：
 

content/zh-cn/docs/concepts/workloads/pods/pod-lifecycle.md

@@ -71,7 +71,7 @@ assigning a Pod to a specific node is called _binding_, and the process of selec
 which node to use is called _scheduling_.
 Once a Pod has been scheduled and is bound to a node, Kubernetes tries
 to run that Pod on the node. The Pod runs on that node until it stops, or until the Pod
-is [terminated](#pod-termination); if Kubernetes isn't able start the Pod on the selected
+is [terminated](#pod-termination); if Kubernetes isn't able to start the Pod on the selected
 node (for example, if the node crashes before the Pod starts), then that particular Pod
 never starts.
 -->