[zh-cn] sync cron-jobs pods/_index

Signed-off-by: xin.li <xin.li@daocloud.io>

content/zh-cn/docs/concepts/workloads/controllers/cron-jobs.md

@@ -128,9 +128,9 @@ The `.spec.schedule` field is required. The value of that field follows the [Cro
 ```
 
 <!--
-For example, `0 0 13 * 5` states that the task must be started every Friday at midnight, as well as on the 13th of each month at midnight.
+For example, `0 3 * * 1` means this task is scheduled to run weekly on a Monday at 3 AM.
 -->
-例如 `0 0 13 * 5` 表示此任务必须在每个星期五的午夜以及每个月的 13 日的午夜开始。
+例如 `0 0 13 * 5` 表示此任务计划于每周一凌晨 3 点运行。
 
 <!--
 The format also includes extended "Vixie cron" step values. As explained in the

content/zh-cn/docs/concepts/workloads/pods/_index.md

@@ -589,7 +589,7 @@ Pods, the kubelet directly supervises each static Pod (and restarts it if it fai
 <!--
 Static Pods are always bound to one {{< glossary_tooltip term_id="kubelet" >}} on a specific node.
 The main use for static Pods is to run a self-hosted control plane: in other words,
-using the kubelet to supervise the individual [control plane components](/docs/concepts/overview/components/#control-plane-components).
+using the kubelet to supervise the individual [control plane components](/docs/concepts/architecture/#control-plane-components).
 
 The kubelet automatically tries to create a {{< glossary_tooltip text="mirror Pod" term_id="mirror-pod" >}}
 on the Kubernetes API server for each static Pod.
@@ -599,7 +599,7 @@ but cannot be controlled from there. See the guide [Create static Pods](/docs/ta
 静态 Pod 通常绑定到某个节点上的 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}。
 其主要用途是运行自托管的控制面。
 在自托管场景中，使用 `kubelet`
-来管理各个独立的[控制面组件](/zh-cn/docs/concepts/overview/components/#control-plane-components)。
+来管理各个独立的[控制面组件](/zh-cn/docs/concepts/architecture/#control-plane-components)。
 
 `kubelet` 自动尝试为每个静态 Pod 在 Kubernetes API
 服务器上创建一个{{< glossary_tooltip text="镜像 Pod" term_id="mirror-pod" >}}。