From c1d3db08c9ceadc928121ecec1bc579ed5c4f405 Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Wed, 22 Sep 2021 03:43:43 +0300
Subject: [PATCH] [zh] using-api/health-checks.md: use consistent casing

---
 content/zh/docs/reference/using-api/health-checks.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/zh/docs/reference/using-api/health-checks.md b/content/zh/docs/reference/using-api/health-checks.md
index 4def388ccc..d22c88e43d 100644
--- a/content/zh/docs/reference/using-api/health-checks.md
+++ b/content/zh/docs/reference/using-api/health-checks.md
@@ -29,7 +29,7 @@ The Kubernetes API server provides 3 API endpoints (`healthz`, `livez` and `read
 The `healthz` endpoint is deprecated (since Kubernetes v1.16), and you should use the more specific `livez` and `readyz` endpoints instead.
 The `livez` endpoint can be used with the `--livez-grace-period` [flag](/docs/reference/command-line-tools-reference/kube-apiserver) to specify the startup duration.
 For a graceful shutdown you can specify the `--shutdown-delay-duration` [flag](/docs/reference/command-line-tools-reference/kube-apiserver) with the `/readyz` endpoint.
-Machines that check the `health`/`livez`/`readyz` of the API server should rely on the HTTP status code.
+Machines that check the `healthz`/`livez`/`readyz` of the API server should rely on the HTTP status code.
 A status code `200` indicates the API server is `healthy`/`live`/`ready`, depending of the called endpoint.
 The more verbose options shown below are intended to be used by human operators to debug their cluster or specially the state of the API server.
 -->
@@ -37,7 +37,7 @@ Kubernetes API 服务器提供 3 个 API 端点（`healthz`、`livez` 和 `ready
 `healthz` 端点已被弃用（自 Kubernetes v1.16 起），你应该使用更为明确的 `livez` 和 `readyz` 端点。
 `livez` 端点可与 `--livez-grace-period` [标志](/zh/docs/reference/command-line-tools-reference/kube-apiserver)一起使用，来指定启动持续时间。
 为了正常关机，你可以使用 `/readyz` 端点并指定 `--shutdown-delay-duration` [标志](/zh/docs/reference/command-line-tools-reference/kube-apiserver)。
-检查 API 服务器的 `health`/`livez`/`readyz` 端点的机器应依赖于 HTTP 状态代码。
+检查 API 服务器的 `healthz`/`livez`/`readyz` 端点的机器应依赖于 HTTP 状态代码。
 状态码 `200` 表示 API 服务器是 `healthy`、`live` 还是 `ready`，具体取决于所调用的端点。
 以下更详细的选项供操作人员使用，用来调试其集群或专门调试 API 服务器的状态。
 
@@ -46,7 +46,7 @@ Kubernetes API 服务器提供 3 个 API 端点（`healthz`、`livez` 和 `ready
 
 <!-- 
 For all endpoints you can use the `verbose` parameter to print out the checks and their status.
-This can be useful for a human operator to debug the current status of the Api server, it is not intended to be consumed by a machine:
+This can be useful for a human operator to debug the current status of the API server, it is not intended to be consumed by a machine:
 -->
 对于所有端点，都可以使用 `verbose` 参数来打印检查项以及检查状态。
 这对于操作人员调试 API 服务器的当前状态很有用，这些不打算给机器使用：
@@ -130,12 +130,12 @@ healthz check passed
 {{< feature-state state="alpha" >}}
 
 <!-- 
-Each individual health check exposes an http endpoint and could can be checked individually.
+Each individual health check exposes an HTTP endpoint and could can be checked individually.
 The schema for the individual health checks is `/livez/<healthcheck-name>` where `livez` and `readyz` and be used to indicate if you want to check the liveness or the readiness of the API server.
 The `<healthcheck-name>` path can be discovered using the `verbose` flag from above and take the path between `[+]` and `ok`.
 These individual health checks should not be consumed by machines but can be helpful for a human operator to debug a system:
 -->
-每个单独的健康检查都会公开一个 http 端点，并且可以单独检查。
+每个单独的健康检查都会公开一个 HTTP 端点，并且可以单独检查。
 单个运行状况检查的模式为 `/livez/<healthcheck-name>`，其中 `livez` 和 `readyz` 表明你要检查的是 API 服务器是否存活或就绪。
 `<healthcheck-name>` 的路径可以通过上面的 `verbose` 参数发现 ，并采用 `[+]` 和 `ok` 之间的路径。
 这些单独的健康检查不应由机器使用，但对于操作人员调试系统而言，是有帮助的：