sync /pods/_index init-container /labels-annotations-taints/_index

sync /pods/_index  init-container  /labels-annotations-taints/_index

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

@@ -278,7 +278,7 @@ You should set the `.spec.os.name` field to either `windows` or `linux` to indic
 In Kubernetes v{{< skew currentVersion >}}, the value you set for this field has no
 effect on {{< glossary_tooltip text="scheduling" term_id="kube-scheduler" >}} of the pods.
 Setting the `.spec.os.name` helps to identify the pod OS
-authoratitively and is used for validation. The kubelet refuses to run a Pod where you have
+authoritatively and is used for validation. The kubelet refuses to run a Pod where you have
 specified a Pod OS, if this isn't the same as the operating system for the node where
 that kubelet is running.
 The [Pod security standards](/docs/concepts/security/pod-security-standards/) also use this

content/zh-cn/docs/concepts/workloads/pods/init-containers.md

@@ -167,7 +167,7 @@ Here are some ideas for how to use init containers:
 * 等待一个 Service 完成创建，通过类似如下 Shell 命令：
 
   ```shell
-  for i in {1..100}; do sleep 1; if dig myservice; then exit 0; fi; done; exit 1
+  for i in {1..100}; do sleep 1; if nslookup myservice; then exit 0; fi; done; exit 1
   ```
 
 <!--