update reference doc

Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>

docs/case-studies/multi-cluster.md

@@ -145,7 +145,7 @@ Handling connection for 8080
 
 The following figure displays the architecture of a multi-cluster application. All the configurations (including Application, Policy and Workflow) lives in the hub cluster. Only the resources (like deployment or service) will be dispatched in to managed clusters.
 
-The policies mainly takes charge of describing the destination of the resources and how they should be overrided. The real executor of the resource dispatch is the workflow. In each `deploy` workflow step, it will refer to some policies, override the default configuration, and dispatch the resources.
+The policies mainly takes charge of describing the destination of the resources and how they should be overridden. The real executor of the resource dispatch is the workflow. In each `deploy` workflow step, it will refer to some policies, override the default configuration, and dispatch the resources.
 
 ![multi-cluster-arch](../resources/multi-cluster-arch.jpg)
 

docs/end-user/policies/references.md

@@ -10,6 +10,8 @@ This documentation will walk through the built-in policies.
 
 Allow configuration drift for applied resources.
 
+It's generally used in [one time delivery only without continuous management](../policies/apply-once) scenario.
+
 **Parameter**
 
 |   Name    |  Type  |           Description            |
@@ -44,7 +46,9 @@ spec:
 
 **Overview**
 
-Configure the garbage collection behaviour for the application.
+Configure the garbage collection behavior for the application.
+
+It's used in [garbage collection](../policies/gc) scenario. It can be used to configure the collection policy, e.g. don't delete the legacy resources when update.
 
 **Parameter**
 
@@ -127,6 +131,8 @@ spec:
 
 Describe the configuration to override when deploying resources.
 
+Override policy need to use along with the deploy workflow step.
+
 **Parameter**
 
 |   Name    |  Type  |           Description            |

i18n/zh/docusaurus-plugin-content-docs/current/end-user/policies/references.md

@@ -10,6 +10,8 @@ title: 内置策略类型
 
 允许被部署资源的配置漂移。
 
+通常用于仅[单次部署](../policies/apply-once)，不做持续发布的场景 scenario.
+
 **参数**
 
 |   参数名    |  类型  |           说明            |
@@ -44,7 +46,7 @@ spec:
 
 **简介**
 
-为应用配置垃圾回收行为。
+为应用配置垃圾回收行为。 通常用于 [资源回收](../policies/gc) 场景，可以配置资源的回收策略，如不回收。
 
 **参数**
 

i18n/zh/docusaurus-plugin-content-docs/version-v1.4/end-user/policies/references.md

@@ -10,6 +10,8 @@ title: 内置策略类型
 
 允许被部署资源的配置漂移。
 
+通常用于仅[单次部署](../policies/apply-once)，不做持续发布的场景 scenario.
+
 **参数**
 
 |   参数名    |  类型  |           说明            |
@@ -44,7 +46,7 @@ spec:
 
 **简介**
 
-为应用配置垃圾回收行为。
+为应用配置垃圾回收行为。 通常用于 [资源回收](../policies/gc) 场景，可以配置资源的回收策略，如不回收。
 
 **参数**
 

versioned_docs/version-v1.3/case-studies/multi-cluster.md

@@ -145,7 +145,7 @@ Handling connection for 8080
 
 The following figure displays the architecture of a multi-cluster application. All the configurations (including Application, Policy and Workflow) lives in the hub cluster. Only the resources (like deployment or service) will be dispatched in to managed clusters.
 
-The policies mainly takes charge of describing the destination of the resources and how they should be overrided. The real executor of the resource dispatch is the workflow. In each `deploy` workflow step, it will refer to some policies, override the default configuration, and dispatch the resources.
+The policies mainly takes charge of describing the destination of the resources and how they should be overridden. The real executor of the resource dispatch is the workflow. In each `deploy` workflow step, it will refer to some policies, override the default configuration, and dispatch the resources.
 
 ![multi-cluster-arch](../resources/multi-cluster-arch.jpg)
 

versioned_docs/version-v1.3/end-user/policies/references.md

@@ -44,7 +44,7 @@ spec:
 
 **Overview**
 
-Configure the garbage collection behaviour for the application.
+Configure the garbage collection behavior for the application.
 
 **Parameter**
 

versioned_docs/version-v1.4/case-studies/multi-cluster.md

@@ -145,7 +145,7 @@ Handling connection for 8080
 
 The following figure displays the architecture of a multi-cluster application. All the configurations (including Application, Policy and Workflow) lives in the hub cluster. Only the resources (like deployment or service) will be dispatched in to managed clusters.
 
-The policies mainly takes charge of describing the destination of the resources and how they should be overrided. The real executor of the resource dispatch is the workflow. In each `deploy` workflow step, it will refer to some policies, override the default configuration, and dispatch the resources.
+The policies mainly takes charge of describing the destination of the resources and how they should be overridden. The real executor of the resource dispatch is the workflow. In each `deploy` workflow step, it will refer to some policies, override the default configuration, and dispatch the resources.
 
 ![multi-cluster-arch](../resources/multi-cluster-arch.jpg)
 

versioned_docs/version-v1.4/end-user/policies/references.md

@@ -10,6 +10,8 @@ This documentation will walk through the built-in policies.
 
 Allow configuration drift for applied resources.
 
+It's generally used in [one time delivery only without continuous management](../policies/apply-once) scenario.
+
 **Parameter**
 
 |   Name    |  Type  |           Description            |
@@ -44,7 +46,9 @@ spec:
 
 **Overview**
 
-Configure the garbage collection behaviour for the application.
+Configure the garbage collection behavior for the application.
+
+It's used in [garbage collection](../policies/gc) scenario. It can be used to configure the collection policy, e.g. don't delete the legacy resources when update.
 
 **Parameter**
 
@@ -127,6 +131,8 @@ spec:
 
 Describe the configuration to override when deploying resources.
 
+Override policy need to use along with the deploy workflow step.
+
 **Parameter**
 
 |   Name    |  Type  |           Description            |