Merge pull request #34804 from mengjiao-liu/fix-deployment-nginx-tag-zh

[zh] Resync deployment page

content/zh-cn/docs/concepts/workloads/controllers/deployment.md

@@ -21,8 +21,8 @@ weight: 10
 <!-- overview -->
 
 <!--
-A _Deployment_ provides declarative updates for [Pods](/docs/concepts/workloads/pods/pod/) and
-[ReplicaSets](/docs/concepts/workloads/controllers/replicaset/).
+A _Deployment_ provides declarative updates for {{< glossary_tooltip text="Pods" term_id="pod" >}} and
+{{< glossary_tooltip term_id="replica-set" text="ReplicaSets" >}}.
 -->
 一个 Deployment 为 {{< glossary_tooltip text="Pod" term_id="pod" >}}
 和 {{< glossary_tooltip term_id="replica-set" text="ReplicaSet" >}}
@@ -604,9 +604,9 @@ as per the update and start scaling that up, and rolls over the ReplicaSet that
 <!--
 For example, suppose you create a Deployment to create 5 replicas of `nginx:1.14.2`,
 but then update the Deployment to create 5 replicas of `nginx:1.16.1`, when only 3
-replicas of `nginx:1.7.9` had been created. In that case, the Deployment immediately starts
-killing the 3 `nginx:1.7.9` Pods that it had created, and starts creating
-`nginx:1.9.1` Pods. It does not wait for the 5 replicas of `nginx:1.14.2` to be created
+replicas of `nginx:1.14.2` had been created. In that case, the Deployment immediately starts
+killing the 3 `nginx:1.14.2` Pods that it had created, and starts creating
+`nginx:1.16.1` Pods. It does not wait for the 5 replicas of `nginx:1.14.2` to be created
 before changing course.
 -->
 例如，假定你在创建一个 Deployment 以生成 `nginx:1.14.2` 的 5 个副本，但接下来
@@ -798,7 +798,7 @@ Deployment 被触发上线时，系统就会创建 Deployment 的新的修订版
     Labels:  app=nginx
     Containers:
      nginx:
-      Image:        nginx:1.91
+      Image:        nginx:1.161
       Port:         80/TCP
       Host Port:    0/TCP
       Environment:  <none>
@@ -865,7 +865,7 @@ Follow the steps given below to check the rollout history:
    复制动作发生在修订版本创建时。你可以通过以下方式设置 `CHANGE-CAUSE` 消息：
 
    <!--
-   * Annotating the Deployment with `kubectl annotate deployment/nginx-deployment kubernetes.io/change-cause="image updated to 1.9.1"`
+   * Annotating the Deployment with `kubectl annotate deployment/nginx-deployment kubernetes.io/change-cause="image updated to 1.16.1"`
    * Manually editing the manifest of the resource.
    -->
    * 使用 `kubectl annotate deployment/nginx-deployment kubernetes.io/change-cause="image updated to 1.16.1"`
@@ -1854,8 +1854,8 @@ can create multiple Deployments, one for each release, following the canary patt
 ## 金丝雀部署 {#canary-deployment}
 
 如果要使用 Deployment 向用户子集或服务器子集上线版本，
-则可以遵循[资源管理](/zh-cn/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)
-所描述的金丝雀模式，创建多个 Deployment，每个版本一个。
+则可以遵循[资源管理](/zh-cn/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)所描述的金丝雀模式，
+创建多个 Deployment，每个版本一个。
 
 <!--
 ## Writing a Deployment Spec