Merge pull request #44250 from asa3311/sync-zh-88

[zh] sync change-package-repository /tasks/debug/debug-cluster/_index verify-kubectl

content/zh-cn/docs/tasks/administer-cluster/kubeadm/change-package-repository.md

@@ -223,7 +223,7 @@ version.
 
 在从一个 Kubernetes 小版本升级到另一个版本时，应执行此步骤以获取所需 Kubernetes 小版本的软件包访问权限。
 
-{{< tabs name="k8s_install_versions" >}}
+{{< tabs name="k8s_upgrade_versions" >}}
 {{% tab name="Ubuntu、Debian 或 HypriotOS" %}}
 
 <!--

content/zh-cn/docs/tasks/debug/debug-cluster/_index.md

@@ -313,7 +313,7 @@ This is an incomplete list of things that could go wrong, and how to adjust your
 - Network partition within cluster, or between cluster and users
 - Crashes in Kubernetes software
 - Data loss or unavailability of persistent storage (e.g. GCE PD or AWS EBS volume)
-- Operator error, for example misconfigured Kubernetes software or application software
+- Operator error, for example, misconfigured Kubernetes software or application software
 -->
 ### 故障原因 {#contributing-causes}
 
@@ -329,7 +329,7 @@ This is an incomplete list of things that could go wrong, and how to adjust your
 - API server VM shutdown or apiserver crashing
   - Results
     - unable to stop, update, or start new pods, services, replication controller
-    - existing pods and services should continue to work normally, unless they depend on the Kubernetes API
+    - existing pods and services should continue to work normally unless they depend on the Kubernetes API
 - API server backing storage lost
   - Results
     - the kube-apiserver component fails to start successfully and become healthy
@@ -401,7 +401,7 @@ This is an incomplete list of things that could go wrong, and how to adjust your
 <!--
 ### Mitigations
 
-- Action: Use IaaS provider's automatic VM restarting feature for IaaS VMs
+- Action: Use the IaaS provider's automatic VM restarting feature for IaaS VMs
   - Mitigates: Apiserver VM shutdown or apiserver crashing
   - Mitigates: Supporting services VM shutdown or crashes
 

content/zh-cn/docs/tasks/tools/included/verify-kubectl.md

@@ -43,7 +43,8 @@ kubectl cluster-info
 <!-- 
 If you see a URL response, kubectl is correctly configured to access your cluster.
 
-If you see a message similar to the following, kubectl is not configured correctly or is not able to connect to a Kubernetes cluster.
+If you see a message similar to the following, kubectl is not configured correctly
+or is not able to connect to a Kubernetes cluster.
 -->
 如果返回一个 URL，则意味着 kubectl 成功地访问到了你的集群。
 
@@ -55,9 +56,11 @@ The connection to the server <server-name:port> was refused - did you specify th
 ```
 
 <!-- 
-For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like Minikube to be installed first and then re-run the commands stated above.
+For example, if you are intending to run a Kubernetes cluster on your laptop (locally),
+you will need a tool like Minikube to be installed first and then re-run the commands stated above.
 
-If kubectl cluster-info returns the url response but you can't access your cluster, to check whether it is configured properly, use:
+If kubectl cluster-info returns the url response but you can't access your cluster,
+to check whether it is configured properly, use:
 -->
 例如，如果你想在自己的笔记本上（本地）运行 Kubernetes 集群，你需要先安装一个 Minikube
 这样的工具，然后再重新运行上面的命令。
@@ -72,9 +75,8 @@ kubectl cluster-info dump
 ### Troubleshooting the 'No Auth Provider Found' error message {#no-auth-provider-found}
 
 In Kubernetes 1.26, kubectl removed the built-in authentication for the following cloud
-providers' managed Kubernetes offerings.
-These providers have released kubectl plugins to provide the cloud-specific authentication.
-For instructions, refer to the following provider documentation:
+providers' managed Kubernetes offerings. These providers have released kubectl plugins
+to provide the cloud-specific authentication. For instructions, refer to the following provider documentation:
 -->
 ### 排查"找不到身份验证提供商"的错误信息    {#no-auth-provider-found}