[zh-cn]sync pod-lifecycle slis

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

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

@@ -2,11 +2,13 @@
 title: Pod 的生命周期
 content_type: concept
 weight: 30
+math: true
 ---
 <!--
 title: Pod Lifecycle
 content_type: concept
 weight: 30
+math: true
 -->
 
 <!-- overview -->
@@ -1049,15 +1051,17 @@ a time longer than the liveness interval would allow.
 你不再需要配置一个较长的存活态探测时间间隔，只需要设置另一个独立的配置选定，
 对启动期间的容器执行探测，从而允许使用远远超出存活态时间间隔所允许的时长。
 
+<!-- ensure front matter contains math: true -->
+
 <!--
 If your container usually starts in more than
-`initialDelaySeconds + failureThreshold × periodSeconds`, you should specify a
+\\( initialDelaySeconds + failureThreshold \times  periodSeconds \\), you should specify a
 startup probe that checks the same endpoint as the liveness probe. The default for
 `periodSeconds` is 10s. You should then set its `failureThreshold` high enough to
 allow the container to start, without changing the default values of the liveness
 probe. This helps to protect against deadlocks.
 -->
-如果你的容器启动时间通常超出 `initialDelaySeconds + failureThreshold × periodSeconds`
+如果你的容器启动时间通常超出 \\( initialDelaySeconds + failureThreshold \times  periodSeconds \\)
 总值，你应该设置一个启动探测，对存活态探针所使用的同一端点执行检查。
 `periodSeconds` 的默认值是 10 秒。你应该将其 `failureThreshold` 设置得足够高，
 以便容器有充足的时间完成启动，并且避免更改存活态探针所使用的默认值。

content/zh-cn/docs/reference/instrumentation/slis.md

@@ -3,6 +3,8 @@ title: Kubernetes 组件 SLI 指标
 linkTitle: 服务水平指示器指标
 content_type: reference
 weight: 20
+description: >-
+  用于衡量 Kubernetes 组件可靠性和性能的高级指标。
 ---
 <!--
 reviewers:
@@ -11,6 +13,8 @@ title: Kubernetes Component SLI Metrics
 linkTitle: Service Level Indicator Metrics
 content_type: reference
 weight: 20
+description: >-
+  High-level indicators for measuring the reliability and performance of Kubernetes components.
 -->
 
 <!-- overview -->