[zh]Resync tasks files[7]

content/zh/docs/tasks/configure-pod-container/pull-image-private-registry.md

@@ -109,7 +109,8 @@ kubectl create secret docker-registry regcred \
 <!--
 where:
 
-* `<your-registry-server>` is your Private Docker Registry FQDN. (https://index.docker.io/v1/ for DockerHub)
+* `<your-registry-server>` is your Private Docker Registry FQDN.
+  Use `https://index.docker.io/v2/` for DockerHub.
 * `<your-name>` is your Docker username.
 * `<your-pword>` is your Docker password.
 * `<your-email>` is your Docker email.
@@ -119,7 +120,7 @@ You have successfully set your Docker credentials in the cluster as a Secret cal
 在这里：
 
 * `<your-registry-server>` 是你的私有 Docker 仓库全限定域名（FQDN）。
-  (参考 https://index.docker.io/v1/ 中关于 DockerHub 的部分)
+  DockerHub 使用 `https://index.docker.io/v2/`。
 * `<your-name>` 是你的 Docker 用户名。
 * `<your-pword>` 是你的 Docker 密码。
 * `<your-email>` 是你的 Docker 邮箱。
@@ -129,7 +130,7 @@ You have successfully set your Docker credentials in the cluster as a Secret cal
 <!--
 ## Inspecting the Secret `regcred`
 
-To understand the contents of the `regcred` Secret you just created, start by viewing the Secret in YAML format:
+To understand the contents of the `regcred` Secret you created, start by viewing the Secret in YAML format:
 -->
 ## 检查 Secret `regcred`
 
@@ -231,7 +232,8 @@ janedoe/jdoe-private:v1
 
 <!--
 To pull the image from the private registry, Kubernetes needs credentials.
-The `imagePullSecrets` field in the configuration file specifies that Kubernetes should get the credentials from a Secret named `regcred`.
+The `imagePullSecrets` field in the configuration file specifies that
+Kubernetes should get the credentials from a Secret named `regcred`.
 
 Create a Pod that uses your Secret, and verify that the Pod is running:
 -->