diff --git a/content/zh-cn/docs/reference/glossary/statefulset.md b/content/zh-cn/docs/reference/glossary/statefulset.md
index e94318e78a..de43a53988 100644
--- a/content/zh-cn/docs/reference/glossary/statefulset.md
+++ b/content/zh-cn/docs/reference/glossary/statefulset.md
@@ -14,13 +14,12 @@ tags:
 ---
 
 <!--
----
 title: StatefulSet
 id: statefulset
 date: 2018-04-12
 full_link: /docs/concepts/workloads/controllers/statefulset/
 short_description: >
-  Manages deployment and scaling of a set of Pods, with durable storage and persistent identifiers for each Pod.
+  A StatefulSet manages deployment and scaling of a set of Pods, with durable storage and persistent identifiers for each Pod.
 
 aka: 
 tags:
@@ -28,7 +27,6 @@ tags:
 - core-object
 - workload
 - storage
----
 -->
 
 <!--
@@ -39,7 +37,7 @@ StatefulSet 用来管理某 {{< glossary_tooltip text="Pod" term_id="pod" >}} 
 <!--more--> 
 
 <!--
-Like a {{< glossary_tooltip term_id="deployment" >}}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods. These pods are created from the same spec, but are not interchangeable&#58; each has a persistent identifier that it maintains across any rescheduling.
+Like a {{< glossary_tooltip term_id="deployment" >}}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of its Pods. These pods are created from the same spec, but are not interchangeable&#58; each has a persistent identifier that it maintains across any rescheduling.
 -->
 
 和 {{< glossary_tooltip text="Deployment" term_id="deployment" >}} 类似，
diff --git a/content/zh-cn/docs/reference/kubectl/conventions.md b/content/zh-cn/docs/reference/kubectl/conventions.md
index 2f6cc0f190..1f67fdb282 100644
--- a/content/zh-cn/docs/reference/kubectl/conventions.md
+++ b/content/zh-cn/docs/reference/kubectl/conventions.md
@@ -46,16 +46,20 @@ For a stable output in a script:
 ## 子资源    {#subresources}
 
 <!--
-* You can use the `--subresource` alpha flag for kubectl commands like `get`, `patch`,
+* You can use the `--subresource` beta flag for kubectl commands like `get`, `patch`,
 `edit` and `replace` to fetch and update subresources for all resources that
 support them. Currently, only the `status` and `scale` subresources are supported.
+  * For `kubectl edit`, the `scale` subresource is not supported. If you use  `--subresource` with
+    `kubectl edit` and specify `scale` as the subresource, the command will error out.
 * The API contract against a subresource is identical to a full resource. While updating the
 `status` subresource to a new value, keep in mind that the subresource could be potentially
 reconciled by a controller to a different value.
 -->
 
-* 你可以将 `--subresource` alpha 标志用于 kubectl 命令，例如 `get`、`patch`、`edit` 和 `replace`
+* 你可以将 `--subresource` Beta 标志用于 kubectl 命令，例如 `get`、`patch`、`edit` 和 `replace`
   来获取和更新所有支持子资源的资源的子资源。目前，仅支持 `status` 和 `scale` 子资源。
+  * 对于 `kubectl edit`，不支持 `scale` 子资源。如果将 `--subresource` 与 `kubectl edit` 一起使用，
+    并指定 `scale` 作为子资源，则命令将会报错。
 * 针对子资源的 API 协定与完整资源相同。在更新 `status` 子资源为一个新值时，请记住，
   子资源可能是潜在的由控制器调和为不同的值。