diff --git a/docs/core-concepts/yurt-app-manager.md b/docs/core-concepts/yurt-app-manager.md
index bee325c0c0..0998d9f23d 100644
--- a/docs/core-concepts/yurt-app-manager.md
+++ b/docs/core-concepts/yurt-app-manager.md
@@ -28,7 +28,7 @@ Yurt-App-Manager是OpenYurt集群提供边缘单元化管理的功能组件，
 
 - 流量的单元化： Service 拓扑，通过简单配置来限制Service后端Endpoint的访问范围，例如只能由相同节点池的节点访问，或者只能本节点访问。
 
-而Yurt-App-Manager是 Kubernetes 的一个标准扩展，它可以配合 Kubernetes 使用，提供 NodePool 和 UnitedDeployment 两种控制器，从主机维度和应用维度来提供边缘场景下节点和应用的运维能力。
+而Yurt-App-Manager是 Kubernetes 的一个标准扩展，它可以配合 Kubernetes 使用，提供 NodePool 和 YurtAppSet(之前名为UnitedDeployment) 两种控制器，从主机维度和应用维度来提供边缘场景下节点和应用的运维能力。
 
 ## 边缘节点池概述
 
@@ -57,13 +57,13 @@ NodePool 以节点组的维度对节点划分做了更高维度的抽象，可
 
 - 相同应用的多个Deployment，除了name，nodeselectors, replicas 这些特性外，其他的差异化配置比较小。
 
-单元化部署（UnitedDeployment）是OpenYurt默认提供Yurt-App-Manager组件所提供的能力，是kubernetes CRD 资源，通过更上层次的抽象，对这些子的Deployment 进行统一管理：create/update/delete。
+单元化部署（YurtAppSet）是OpenYurt默认提供Yurt-App-Manager组件所提供的能力，是kubernetes CRD 资源，通过更上层次的抽象，对这些子的Deployment 进行统一管理：create/update/delete。
 
 
 
 ![img](https://intranetproxy.alipay.com/skylark/lark/0/2022/png/31456432/1641823282158-8e00965d-e17e-4a79-912c-01589f98217e.png)
 
-UnitedDeployment 控制器可以提供一个模板来定义应用，并通过管理多个 workload 来匹配下面不同的区域。 每个 UnitedDeployment 下每个区域的 workload 被称为 pool， 目前 pool 支持使用两种workload： `StatefulSet` 和 `Deployment`。控制器会根据 UnitedDeployment 中pool的配置创建子的workload 资源对象，每个资源对象都有一个期望的 `replicas` Pod 数量。通过一个UnitedDeployment 实例就可以自动维护多个 Deployment 或者 Statefulset 资源，同时还能具备replicas 等的差异化配置。
+YurtAppSet 控制器可以提供一个模板来定义应用，并通过管理多个 workload 来匹配下面不同的区域。 每个 YurtAppSet 下每个区域的 workload 被称为 pool， 目前 pool 支持使用两种workload： `StatefulSet` 和 `Deployment`。控制器会根据 YurtAppSet 中pool的配置创建子的workload 资源对象，每个资源对象都有一个期望的 `replicas` Pod 数量。通过一个 YurtAppSet 实例就可以自动维护多个 Deployment 或者 Statefulset 资源，同时还能具备replicas 等的差异化配置。
 
 
 
@@ -77,8 +77,8 @@ UnitedDeployment 控制器可以提供一个模板来定义应用，并通过管
 
 更多关于 Yurt-App-Manager 的讨论请参考社区 issue 和 pull request：
 
-- issue124：[UnitedDeployment usages]( https://github.com/openyurtio/openyurt/issues/124)
-- issue171：[ [feature request\] the definition of NodePool and UnitedDeployment](https://github.com/openyurtio/openyurt/issues/171)
+- issue124：[YurtAppSet usages]( https://github.com/openyurtio/openyurt/issues/124)
+- issue171：[ [feature request\] the definition of NodePool and YurtAppSet](https://github.com/openyurtio/openyurt/issues/171)
 
 - pull request 173： [[proposal\] add nodepool and uniteddployment crd proposal](https://link.zhihu.com/?target=https%3A//github.com/alibaba/openyurt/pull/173)
 
diff --git a/docs/core-concepts/yurthub.md b/docs/core-concepts/yurthub.md
index 4307d0f193..78b4bdc1c2 100644
--- a/docs/core-concepts/yurthub.md
+++ b/docs/core-concepts/yurthub.md
@@ -16,7 +16,8 @@ OpenYurt supports edge autonomy, which means even under the circumstance of netw
 
 ### 2）Traffic Closure
 
-In the native Kubernetes, the endpoints of a service are distributed among the whole cluster. But in OpenYurt we can divided nodes into nodepools, and manage them at the granularity of nodepool. On the base of it, we can also manage resources in each nodepool individually, such as using UnitedDeployment to manage pods in different nodepools.
+
+In the native Kubernetes, the endpoints of a service are distributed among the whole cluster. But in OpenYurt we can divided nodes into nodepools, and manage them at the granularity of nodepool. On the base of it, we can also manage resources in each nodepool individually, such as using YurtAppSet to manage pods in different nodepools.
 
 In the scenario of edge computing, resources in one nodepool are often independent on those in other nodepools, and nodes sometimes can only reach the nodes in the same nodepools. To meet this need, `YurtHub` provides the capability of traffic closure to ensure the client can only reach the endpoints in the same nodepool making the traffic closed in the granularity of nodepool.
 
@@ -299,3 +300,4 @@ Output the version of `YurtHub`.
 ```
 
 Working mode of `YurtHub`. It can be "edge" which means `YurtHub` is running on an edge node, or "cloud" which means `YurtHub` is running on a cloud node.
+
diff --git a/docs/installation/openyurt-experience-center/kubeconfig.md b/docs/installation/openyurt-experience-center/kubeconfig.md
index 1eb9503c1f..6bd0e362d2 100644
--- a/docs/installation/openyurt-experience-center/kubeconfig.md
+++ b/docs/installation/openyurt-experience-center/kubeconfig.md
@@ -61,27 +61,27 @@ The corresponding NodePool information can be seen in browser page.
 ```bash
 cat <<EOF | kubectl apply -f -
 apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
+kind: YurtAppSet
 metadata:
   labels:
     controller-tools.k8s.io: "1.0"
-  name: ud-test
+  name: yas-test
   namespace: "183xxxxxxxx"  # Notice: change this with your own namespace
 spec:
   selector:
     matchLabels:
-      app: ud-test
+      app: yas-test
   workloadTemplate:
     deploymentTemplate:
       metadata:
         labels:
-          app: ud-test
+          app: yas-test
       namespace: "183xxxxxxxx"  # Notice: change this with your own namespace
       spec:
         template:
           metadata:
             labels:
-              app: ud-test
+              app: yas-test
           spec:
             containers:
               - name: nginx
diff --git a/docs/user-manuals/iot/edgex-foundry.md b/docs/user-manuals/iot/edgex-foundry.md
index 33ec6ca9f0..3975854216 100644
--- a/docs/user-manuals/iot/edgex-foundry.md
+++ b/docs/user-manuals/iot/edgex-foundry.md
@@ -138,13 +138,13 @@ edgex-sample-hangzhou   true    9         9              9            9
 $ kubectl apply -f https://raw.githubusercontent.com/openyurtio/yurt-device-controller/main/config/setup/crd.yaml
 ```
 
-使用UnitedDeployment在hanghzou节点池中部署一个yurt-device-controller实例
+使用YurtAppSet在hanghzou节点池中部署一个yurt-device-controller实例
 
 ```powershell
 $ export WORKER_NODEPOOL="hangzhou"
 $ cat <<EOF | kubectl apply -f -
 apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
+kind: YurtAppSet
 metadata:
   labels:
     controller-tools.k8s.io: "1.0"
@@ -262,7 +262,7 @@ $ kubectl delete deviceprofile --all
 $ kubectl delete deviceservice --all
 
 # 1.2 删除部署的yurt-device-controller
-$ kubectl delete uniteddeployment yurt-device-controller
+$ kubectl delete yurtappset yurt-device-controller
 $ kubectl delete clusterrolebinding default-cluster-admin
 
 # 1.3 删除device, deviceservice, deviceprofile资源相关的crd
diff --git a/docs/user-manuals/workload/yurt-app-daemon.md b/docs/user-manuals/workload/yurt-app-daemon.md
index 287d8d825c..fe8fc5036a 100644
--- a/docs/user-manuals/workload/yurt-app-daemon.md
+++ b/docs/user-manuals/workload/yurt-app-daemon.md
@@ -2,22 +2,19 @@
 title: YurtAppDaemon
 ---
 
-## 背景介绍
+## Background
 
-在边缘场景中，来自同一区域的边缘节点被分配到同一个节点池中，此时，一般需要在节点池维度部署一些系统组件，例如CoreDNS。 创建节点池时，我们希望自动创建这些系统组件，而无需任何手动操作。
-
-
-
-YurtAppDaemon 确保所有或部分节点池以 Deployment 或 StatefulSet 作为模板运行副本。 随着节点池的创建，这些子部署或状态集也被添加到集群中，子部署或状态集的创建/更新由 YurtAppDaemon 控制器实现。 这些子 Deployments 或 Statefulsets 将在节点池 从集群中移除时被回收，删除 YurtAppDaemon CR 将清理它创建的 Deployments 或 StatefulSets。 YurtAppDaemon 的行为类似于 K8S Daemonset，不同之处在于 YurtAppDaemon 从节点池维度自动创建 K8S 工作负载。
+In edge scenarios, edge nodes from the same region will be assigned to the same NodePool, at which point some system components, such as CoreDNS, will typically need to be deployed in NodePool dimension. When creating the NodePool, we want to create these system components automatically, without any manual operations.
 
+YurtAppDaemon ensures that all or some of the NodePools run replicas with a Deployment or StatefulSet template. As NodePools are created, these sub-Deployments or sub-StatefulSets are added to the cluster and the creation/updating of them are controlled by the YurtAppDaemon controller.
 
 
 
 ![img](https://intranetproxy.alipay.com/skylark/lark/0/2022/png/31456432/1641999454831-b8f2f9f4-c715-4063-8444-b0af22830092.png)
 
-## 用户使用：
+## Usage：
 
-- 创建test1节点池
+- Create test1 NodePool
 
 ```shell
 cat <<EOF | kubectl apply -f -
@@ -37,7 +34,7 @@ spec:
 EOF
 ```
 
-- 创建test2节点池
+- Create test2 NodePool
 
 ```shell
 cat <<EOF | kubectl apply -f -
@@ -55,7 +52,7 @@ spec:
 EOF
 ```
 
-- 将节点加入到节点池
+- Add nodes to the corresponding NodePool
 
 ```shell
  kubectl label node cn-beijing.172.23.142.31 apps.openyurt.io/desired-nodepool=test1
@@ -65,7 +62,7 @@ EOF
  kubectl label node cn-beijing.172.23.142.35 apps.openyurt.io/desired-nodepool=test2
 ```
 
-- 创建YurtAppDaemon
+- Create YurtAppDaemon
 
 ```shell
 cat <<EOF | kubectl apply -f -
@@ -106,7 +103,7 @@ spec:
 EOF
 ```
 
-- 为test1节点池打标签
+- Label test1 NodePool
 
 ```shell
 kubectl label np test1 yurtappdaemon.openyurt.io/type=nginx
@@ -119,7 +116,7 @@ kubectl get deployments.apps
 # Check the Pod
 ```
 
-- 为test2节点池打标签
+- Label test2 NodePool
 
 ```shell
 kubectl label np test2 yurtappdaemon.openyurt.io/type=nginx
@@ -132,7 +129,7 @@ kubectl get deployments.apps
 # Check the Pod
 ```
 
-- 改变YurtAppDaemon
+- Update YurtAppDaemon
 
 ```shell
 # Change yurtappdaemon workloadTemplate replicas to 2
@@ -142,7 +139,7 @@ kubectl get deployments.apps
 # Check the Pod
 ```
 
-- 移除节点池标签
+- Remove NodePool labels
 
 ```shell
 # Remove the nodepool test1 label
@@ -160,11 +157,12 @@ kubectl label np test2 yurtappdaemon.openyurt.io/type-
 # Check the Pod
 ```
 
-## coredns单元化部署案例
 
-> 在openyurt里使用YurtAppDaemon+服务拓扑解决dns解析问题
+## Example for deploying coredns
+
+> Using `YurtAppDaemon`+`service topology` to solve dns resolution problems
 
-- 创建节点池
+- Create NodePool
 ```shell
 cat <<EOF | kubectl apply -f -
 
@@ -186,13 +184,13 @@ spec:
 EOF
 ```
 
-- 节点池增加标签
+- Add label to NodePool
 
 ```shell
 kubectl label np hangzhou yurtappdaemon.openyurt.io/type=coredns
 ```
 
-- 部署coredns
+- Deploy coredns
 
 ```shell
 cat <<EOF | kubectl apply -f -
@@ -386,4 +384,4 @@ subjects:
 
 
 EOF
-``` 
\ No newline at end of file
+``` 
diff --git a/docs/user-manuals/workload/yurt-app-set.md b/docs/user-manuals/workload/yurt-app-set.md
new file mode 100644
index 0000000000..f25358abd8
--- /dev/null
+++ b/docs/user-manuals/workload/yurt-app-set.md
@@ -0,0 +1,154 @@
+---
+title: YurtAppSet
+---
+
+
+
+
+In [the previous article](./node-pool-management.md) we introduced the use of `NodePool`, mainly the creation and management of `NodePool`. 
+Further, we developed the ability to deploy applications unitized based on `NodePool` to improve the efficiency of users' operations.
+
+In this article, we will show how `yurt-app-manager` can help users manage their workload. Assume we already have an OpenYurt cluster built on 
+native kubernetes with at least two nodes.
+
+
+### 1) Create YurtAppSet
+
+- Create `YurtAppSet` by `yurtappset_test.yaml`
+
+```yaml
+apiVersion: apps.openyurt.io/v1alpha1
+kind: YurtAppSet
+metadata:
+  labels:
+    controller-tools.k8s.io: "1.0"
+  name: yas-test
+spec:
+  selector:
+    matchLabels:
+      app: yas-test
+  workloadTemplate:
+    deploymentTemplate:
+      metadata:
+        labels:
+          app: yas-test
+      spec:
+        template:
+          metadata:
+            labels:
+              app: yas-test
+          spec:
+            containers:
+              - name: nginx
+                image: nginx:1.19.3
+  topology:
+    pools:
+    - name: beijing 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - beijing 
+      replicas: 1
+    - name: hangzhou 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - hangzhou 
+      replicas: 2
+      tolerations:
+      - effect: NoSchedule
+        key: apps.openyurt.io/example
+        operator: Exists
+  revisionHistoryLimit: 5 
+```
+
+- Check `YurtAppSet`
+
+```shell
+$ kubectl get yas
+NAME       READY   WORKLOADTEMPLATE   AGE
+yas-test   3       Deployment         43s
+```
+
+
+### 2) Check the deployments created by yurt-app-manager
+
+```shell
+$ kubectl get deploy
+NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
+yas-test-beijing-k5st4    1/1     1            1           54s
+yas-test-hangzhou-2jkj5   2/2     2            2           54s
+
+$ kubectl get pod -l app=yas-test
+NAME                                       READY   STATUS    RESTARTS   AGE
+yas-test-beijing-k5st4-56bc98cc7d-h7h86    1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-8mvn8   1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-vx85t   1/1     Running   0          72s
+```
+
+
+### 3) Add patch to YurtAppSet
+
+- Add the patch field to the file `yurtappset_test.yaml` as follows, lines 36 to 41 of the file
+
+```shell
+$ kubectl get yas yas-test -o yaml
+   
+  topology:
+    pools:
+    - name: beijing 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - beijing 
+      replicas: 1
+      patch:
+        spec:
+          template:
+            spec:
+              containers:
+                - name: nginx
+                  image: nginx:1.19.0
+    - name: hangzhou 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - hangzhou 
+      replicas: 2
+      tolerations:
+  *** 
+```
+
+- This updates the nginx image version to 1.19.0 in the deployments and pods in Beijing NodePool, while keeping the nginx image version at 1.19.3 for the other regions
+
+```shell
+$ kubectl get deploy yas-test-beijing-k5st4 -o yaml
+containers:
+  - image: nginx:1.19.0
+
+$ kubectl get deploy yas-test-hangzhou-2jkj5 -o yaml
+containers:
+  - image: nginx:1.19.3
+```
+
+- After removing the patch, all pods created by YurtAppSet revert back to nginx1.19.3
+
+```shell
+$ kubectl get pod yas-test-beijing-k5st4-974b6958c-t2kfn -o yaml
+containers:
+  - image: nginx:1.19.3
+
+$ kubectl get pod yas-test-hangzhou-2jkj5-64588c484b-8mvn8 -o yaml
+containers:
+  - image: nginx:1.19.3
+```
+
+- Conclusion: Patch solves the upgrade of the NodePool's single attribute and application release.
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/architecture.md b/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/architecture.md
index 0b8a5875e4..5ce1e4b18e 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/architecture.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/architecture.md
@@ -40,7 +40,7 @@ Edge Node上的Kubelet, kube-proxy, Flannel以及其他云原生组件访问云
 
 - **YurtAppManager:**
 
-  - 跨地域的资源及业务负载管理器，目前包括NodePool(节点池管理)，YurtAppSet(之前叫UnitedDeployment)(节点池维度的业务负载管理)，YurtAppDaemon(节点池维度的Daemonset), YurtIngress(节点池维度的Ingress Controller管理器)
+  - 跨地域的资源及业务负载管理器，目前包括NodePool(节点池管理)，YurtAppSet(之前名为UnitedDeployment)(节点池维度的业务负载管理)，YurtAppDaemon(节点池维度的Daemonset), YurtIngress(节点池维度的Ingress Controller管理器)
   - 部署形态： Deployment形态部署在Cloud Node上
 
 - **YurtTunnel(Server/Agent):**
@@ -49,7 +49,7 @@ Edge Node上的Kubelet, kube-proxy, Flannel以及其他云原生组件访问云
 
 - **YurtDeviceController/YurtEdgeXManager:**
   - 用于边缘IOT解决方案的非侵入融合，通过云原生模式管控边缘设备。目前EdgeX Foundry已经无缝集成到OpenYurt架构中。
-  - YurtEdgeXManager以Deployment形态部署在Cloud Node上，YurtDeviceController以YurtAppSet(之前叫UnitedDeployment)形态部署在Edge Node上，每个NodePool上部署一套YurtDeviceController。
+  - YurtEdgeXManager以Deployment形态部署在Cloud Node上，YurtDeviceController以YurtAppSet(之前名为UnitedDeployment)形态部署在Edge Node上，每个NodePool上部署一套YurtDeviceController。
 
 - **NodeResourceManager:**
   - 管理 OpenYurt 集群本地资源的组件，用户可以通过修改集群内 ConfigMap 的定义来动态配置集群内宿主机上的本地资源。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurt-app-manager.md b/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurt-app-manager.md
index bee325c0c0..85454b1fce 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurt-app-manager.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurt-app-manager.md
@@ -28,7 +28,7 @@ Yurt-App-Manager是OpenYurt集群提供边缘单元化管理的功能组件，
 
 - 流量的单元化： Service 拓扑，通过简单配置来限制Service后端Endpoint的访问范围，例如只能由相同节点池的节点访问，或者只能本节点访问。
 
-而Yurt-App-Manager是 Kubernetes 的一个标准扩展，它可以配合 Kubernetes 使用，提供 NodePool 和 UnitedDeployment 两种控制器，从主机维度和应用维度来提供边缘场景下节点和应用的运维能力。
+而Yurt-App-Manager是 Kubernetes 的一个标准扩展，它可以配合 Kubernetes 使用，提供 NodePool 和 YurtAppSet(之前名为UnitedDeployment) 两种控制器，从主机维度和应用维度来提供边缘场景下节点和应用的运维能力。
 
 ## 边缘节点池概述
 
@@ -57,13 +57,13 @@ NodePool 以节点组的维度对节点划分做了更高维度的抽象，可
 
 - 相同应用的多个Deployment，除了name，nodeselectors, replicas 这些特性外，其他的差异化配置比较小。
 
-单元化部署（UnitedDeployment）是OpenYurt默认提供Yurt-App-Manager组件所提供的能力，是kubernetes CRD 资源，通过更上层次的抽象，对这些子的Deployment 进行统一管理：create/update/delete。
+单元化部署（YurtAppSet）是OpenYurt默认提供Yurt-App-Manager组件所提供的能力，是kubernetes CRD 资源，通过更上层次的抽象，对这些子的Deployment 进行统一管理：create/update/delete。
 
 
 
 ![img](https://intranetproxy.alipay.com/skylark/lark/0/2022/png/31456432/1641823282158-8e00965d-e17e-4a79-912c-01589f98217e.png)
 
-UnitedDeployment 控制器可以提供一个模板来定义应用，并通过管理多个 workload 来匹配下面不同的区域。 每个 UnitedDeployment 下每个区域的 workload 被称为 pool， 目前 pool 支持使用两种workload： `StatefulSet` 和 `Deployment`。控制器会根据 UnitedDeployment 中pool的配置创建子的workload 资源对象，每个资源对象都有一个期望的 `replicas` Pod 数量。通过一个UnitedDeployment 实例就可以自动维护多个 Deployment 或者 Statefulset 资源，同时还能具备replicas 等的差异化配置。
+YurtAppSet 控制器可以提供一个模板来定义应用，并通过管理多个 workload 来匹配下面不同的区域。 每个 YurtAppSet 下每个区域的 workload 被称为 pool， 目前 pool 支持使用两种workload： `StatefulSet` 和 `Deployment`。控制器会根据 YurtAppSet 中pool的配置创建子的workload 资源对象，每个资源对象都有一个期望的 `replicas` Pod 数量。通过一个YurtAppSet 实例就可以自动维护多个 Deployment 或者 Statefulset 资源，同时还能具备replicas 等的差异化配置。
 
 
 
@@ -77,8 +77,8 @@ UnitedDeployment 控制器可以提供一个模板来定义应用，并通过管
 
 更多关于 Yurt-App-Manager 的讨论请参考社区 issue 和 pull request：
 
-- issue124：[UnitedDeployment usages]( https://github.com/openyurtio/openyurt/issues/124)
-- issue171：[ [feature request\] the definition of NodePool and UnitedDeployment](https://github.com/openyurtio/openyurt/issues/171)
+- issue124：[YurtAppSet usages]( https://github.com/openyurtio/openyurt/issues/124)
+- issue171：[ [feature request\] the definition of NodePool and YurtAppSet](https://github.com/openyurtio/openyurt/issues/171)
 
 - pull request 173： [[proposal\] add nodepool and uniteddployment crd proposal](https://link.zhihu.com/?target=https%3A//github.com/alibaba/openyurt/pull/173)
 
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurthub.md b/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurthub.md
index e370f040c1..10cb10c825 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurthub.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/core-concepts/yurthub.md
@@ -16,7 +16,7 @@ YurtHub 通过本地缓存资源，使得在云边网络断连的情况下，Pod
 
 ### 2）流量闭环
 
-在原生的 k8s 集群中，服务 Service 资源的后端范围是整个集群。在 OpenYurt 中，可以通过 NodePool 划分节点，对节点进行分区管理。由此，资源的管理可以以节点池为基本单位，比如使用 UnitedDeployment 管理不同节点池中的 Pod 资源。
+在原生的 k8s 集群中，服务 Service 资源的后端范围是整个集群。在 OpenYurt 中，可以通过 NodePool 划分节点，对节点进行分区管理。由此，资源的管理可以以节点池为基本单位，比如使用 YurtAppSet 管理不同节点池中的 Pod 资源。
 
 在这样的背景下，不同节点池中的资源具有一定的独立性，分区中的节点可能要求对 Service 访问流量只在同一区域内流通，而不会跨节点分区访问。因此，YurtHub 提供了流量闭环的功能：将 Service 对应的后端限制在同一节点池中，使得 Service 的访问流量只在同一节点池中流通。
 
@@ -298,3 +298,4 @@ kube-apiserver 的地址。值的格式为 "server1,server2,..."。
 ```
 
 YurtHub 的工作模式。如果值为 "edge"，表示边缘节点；如果值为 "cloud"，表示云端节点。
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/installation/openyurt-experience-center/kubeconfig.md b/i18n/zh/docusaurus-plugin-content-docs/current/installation/openyurt-experience-center/kubeconfig.md
index 2cf5b49396..6519f40965 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/installation/openyurt-experience-center/kubeconfig.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/installation/openyurt-experience-center/kubeconfig.md
@@ -62,7 +62,7 @@ kubectl get nodepool
 # 单元化部署pod
 cat <<EOF | kubectl apply -f -
 apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
+kind: YurtAppSet
 metadata:
   labels:
     controller-tools.k8s.io: "1.0"
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/iot/edgex-foundry.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/iot/edgex-foundry.md
index 928d27ba6b..48baebf94b 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/iot/edgex-foundry.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/iot/edgex-foundry.md
@@ -139,13 +139,13 @@ edgex-sample-hangzhou   true    9         9              9            9
 $ kubectl apply -f https://raw.githubusercontent.com/openyurtio/yurt-device-controller/main/config/setup/crd.yaml
 ```
 
-使用UnitedDeployment在hanghzou节点池中部署一个yurt-device-controller实例
+使用YurtAppSet在hanghzou节点池中部署一个yurt-device-controller实例
 
 ```powershell
 $ export WORKER_NODEPOOL="hangzhou"
 $ cat <<EOF | kubectl apply -f -
 apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
+kind: YurtAppSet
 metadata:
   labels:
     controller-tools.k8s.io: "1.0"
@@ -263,7 +263,7 @@ $ kubectl delete deviceprofile --all
 $ kubectl delete deviceservice --all
 
 # 1.2 删除部署的yurt-device-controller
-$ kubectl delete uniteddeployment yurt-device-controller
+$ kubectl delete yurtappset yurt-device-controller
 $ kubectl delete clusterrolebinding default-cluster-admin
 
 # 1.3 删除device, deviceservice, deviceprofile资源相关的crd
diff --git a/docs/user-manuals/workload/uniteddeployment.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workload/yurt-app-set.md
similarity index 59%
rename from docs/user-manuals/workload/uniteddeployment.md
rename to i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workload/yurt-app-set.md
index 7072a431ff..75aed31466 100644
--- a/docs/user-manuals/workload/uniteddeployment.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workload/yurt-app-set.md
@@ -1,5 +1,5 @@
 ---
-title: UnitedDeployment
+title: YurtAppSet
 ---
 
 
@@ -9,34 +9,33 @@ title: UnitedDeployment
 
 在这篇文章中，我们将展示yurt-app-manager如何帮助用户管理工作负载。假设我们已经拥有一个基于原生kubernetes搭建起来的OpenYurt集群，且至少有两个节点。
 
-## UnitedDeployment用户手册
+## YurtAppSet用户手册
 
-### 创建UnitedDeployment
+### 创建YurtAppSet
 
-- 利用deployment template创建一个UnitedDeployment
+- 通过`yurtappset_test.yaml`创建一个YurtAppSet
 
-```shell
-$ cat <<EOF | kubectl apply -f -
+```yaml
 apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
+kind: YurtAppSet
 metadata:
   labels:
     controller-tools.k8s.io: "1.0"
-  name: ud-test
+  name: yas-test
 spec:
   selector:
     matchLabels:
-      app: ud-test
+      app: yas-test
   workloadTemplate:
     deploymentTemplate:
       metadata:
         labels:
-          app: ud-test
+          app: yas-test
       spec:
         template:
           metadata:
             labels:
-              app: ud-test
+              app: yas-test
           spec:
             containers:
               - name: nginx
@@ -64,16 +63,15 @@ spec:
         key: apps.openyurt.io/example
         operator: Exists
   revisionHistoryLimit: 5 
-EOF
 ```
 
-- 查看UnitedDeployment
+- 查看YurtAppSet
 
 ```shell
-$ kubectl get ud
+$ kubectl get yas
 
-NAME      READY   WORKLOADTEMPLATE   AGE
-ud-test   3       Deployment         120m
+NAME       READY   WORKLOADTEMPLATE   AGE
+yas-test   3       Deployment         43s
 ```
 
 ### 检查由yurt-app-manager组件创建的deployment
@@ -81,25 +79,25 @@ ud-test   3       Deployment         120m
 ```shell
 $ kubectl get deploy
 
-NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
-ud-test-beijing-fp58z    1/1     1            1           122m
-ud-test-hangzhou-xv454   2/2     2            2           122m
-$ kubectl get pod -l app=ud-test
+NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
+yas-test-beijing-k5st4    1/1     1            1           54s
+yas-test-hangzhou-2jkj5   2/2     2            2           54s
+$ kubectl get pod -l app=yas-test
 
-  NAME                                      READY   STATUS    RESTARTS   AGE
-ud-test-beijing-fp58z-787d5b6b54-g4jk6    1/1     Running   0          100m
-ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr   1/1     Running   0          124m
-ud-test-hangzhou-xv454-5cd9c4f6b5-gmbgp   1/1     Running   0          124m
+NAME                                       READY   STATUS    RESTARTS   AGE
+yas-test-beijing-k5st4-56bc98cc7d-h7h86    1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-8mvn8   1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-vx85t   1/1     Running   0          72s
 ```
 
 
 
-### 为UnitedDeployment添加patch功能
+### 为YurtAppSet添加patch功能
 
-- 在文件uniteddeployment_deployment_test.yaml中添加patch字段，如下所示，文件36到41行
+- 在文件yurtappset_test.yaml中添加patch字段，如下所示，文件36到41行
 
 ```shell
-$ kubectl get ud ud-test -o yaml
+$ kubectl get yas yas-test -o yaml
    
   topology:
     pools:
@@ -130,27 +128,27 @@ $ kubectl get ud ud-test -o yaml
   *** 
 ```
 
-- patch能够使得由UnitedDeployment创建的位于北京节点池的deployment和pod中nginx镜像版本为1.19.0，而其他地区的nginx镜像版本为1.19.3。
+- patch能够使得由YurtAppSet创建的位于北京节点池的deployment和pod中nginx镜像版本为1.19.0，而其他地区的nginx镜像版本为1.19.3。
 
 ```shell
-$ kubectl get deploy ud-test-beijing-fp58z -o yaml
+$ kubectl get deploy yas-test-beijing-k5st4 -o yaml
 
 containers:
   - image: nginx:1.19.0
-$ kubectl get deploy ud-test-hangzhou-xv454 -o yaml
+$ kubectl get deploy yas-test-hangzhou-2jkj5 -o yaml
 
 containers:
   - image: nginx:1.19.3
 ```
 
-- 删除后，所有由UnitedDeployment创建的pod又恢复使用相同的镜像nginx1.19.3
+- 删除后，所有由YurtAppSet创建的pod又恢复使用相同的镜像nginx1.19.3
 
 ```shell
-$ kubectl get pod ud-test-beijing-fp58z-787d5b6b54-g4jk6 -o yaml
+$ kubectl get pod yas-test-beijing-k5st4-974b6958c-t2kfn -o yaml
 
 containers:
   - image: nginx:1.19.3
-$ kubectl get pod ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr -o yaml
+$ kubectl get pod yas-test-hangzhou-2jkj5-64588c484b-8mvn8 -o yaml
 containers:
   - image: nginx:1.19.3
 ```
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v0.7.0/user-manuals/workload/uniteddeployment.md b/i18n/zh/docusaurus-plugin-content-docs/version-v0.7.0/user-manuals/workload/uniteddeployment.md
deleted file mode 100644
index 7072a431ff..0000000000
--- a/i18n/zh/docusaurus-plugin-content-docs/version-v0.7.0/user-manuals/workload/uniteddeployment.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: UnitedDeployment
----
-
-
-
-
-在[上一篇文章](./node-pool-management.md) 中我们介绍了节点池的使用，主要是节点池的创建和管理，进一步，我们开发了基于节点池的应用单元化部署能力，提高用户的运维效率。
-
-在这篇文章中，我们将展示yurt-app-manager如何帮助用户管理工作负载。假设我们已经拥有一个基于原生kubernetes搭建起来的OpenYurt集群，且至少有两个节点。
-
-## UnitedDeployment用户手册
-
-### 创建UnitedDeployment
-
-- 利用deployment template创建一个UnitedDeployment
-
-```shell
-$ cat <<EOF | kubectl apply -f -
-apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
-metadata:
-  labels:
-    controller-tools.k8s.io: "1.0"
-  name: ud-test
-spec:
-  selector:
-    matchLabels:
-      app: ud-test
-  workloadTemplate:
-    deploymentTemplate:
-      metadata:
-        labels:
-          app: ud-test
-      spec:
-        template:
-          metadata:
-            labels:
-              app: ud-test
-          spec:
-            containers:
-              - name: nginx
-                image: nginx:1.19.3
-  topology:
-    pools:
-    - name: beijing 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - beijing 
-      replicas: 1
-    - name: hangzhou 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - hangzhou 
-      replicas: 2
-      tolerations:
-      - effect: NoSchedule
-        key: apps.openyurt.io/example
-        operator: Exists
-  revisionHistoryLimit: 5 
-EOF
-```
-
-- 查看UnitedDeployment
-
-```shell
-$ kubectl get ud
-
-NAME      READY   WORKLOADTEMPLATE   AGE
-ud-test   3       Deployment         120m
-```
-
-### 检查由yurt-app-manager组件创建的deployment
-
-```shell
-$ kubectl get deploy
-
-NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
-ud-test-beijing-fp58z    1/1     1            1           122m
-ud-test-hangzhou-xv454   2/2     2            2           122m
-$ kubectl get pod -l app=ud-test
-
-  NAME                                      READY   STATUS    RESTARTS   AGE
-ud-test-beijing-fp58z-787d5b6b54-g4jk6    1/1     Running   0          100m
-ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr   1/1     Running   0          124m
-ud-test-hangzhou-xv454-5cd9c4f6b5-gmbgp   1/1     Running   0          124m
-```
-
-
-
-### 为UnitedDeployment添加patch功能
-
-- 在文件uniteddeployment_deployment_test.yaml中添加patch字段，如下所示，文件36到41行
-
-```shell
-$ kubectl get ud ud-test -o yaml
-   
-  topology:
-    pools:
-    - name: beijing 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - beijing 
-      replicas: 1
-      patch:
-        spec:
-          template:
-            spec:
-              containers:
-                - name: nginx
-                  image: nginx:1.19.0
-    - name: hangzhou 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - hangzhou 
-      replicas: 2
-      tolerations:
-  *** 
-```
-
-- patch能够使得由UnitedDeployment创建的位于北京节点池的deployment和pod中nginx镜像版本为1.19.0，而其他地区的nginx镜像版本为1.19.3。
-
-```shell
-$ kubectl get deploy ud-test-beijing-fp58z -o yaml
-
-containers:
-  - image: nginx:1.19.0
-$ kubectl get deploy ud-test-hangzhou-xv454 -o yaml
-
-containers:
-  - image: nginx:1.19.3
-```
-
-- 删除后，所有由UnitedDeployment创建的pod又恢复使用相同的镜像nginx1.19.3
-
-```shell
-$ kubectl get pod ud-test-beijing-fp58z-787d5b6b54-g4jk6 -o yaml
-
-containers:
-  - image: nginx:1.19.3
-$ kubectl get pod ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr -o yaml
-containers:
-  - image: nginx:1.19.3
-```
-
-- 结论：Patch功能解决了nodepool单属性的升级和应用完整发布。
-
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workload/uniteddeployment.md b/i18n/zh/docusaurus-plugin-content-docs/version-v0.7.0/user-manuals/workload/yurt-app-set.md
similarity index 59%
rename from i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workload/uniteddeployment.md
rename to i18n/zh/docusaurus-plugin-content-docs/version-v0.7.0/user-manuals/workload/yurt-app-set.md
index 7072a431ff..75aed31466 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workload/uniteddeployment.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-v0.7.0/user-manuals/workload/yurt-app-set.md
@@ -1,5 +1,5 @@
 ---
-title: UnitedDeployment
+title: YurtAppSet
 ---
 
 
@@ -9,34 +9,33 @@ title: UnitedDeployment
 
 在这篇文章中，我们将展示yurt-app-manager如何帮助用户管理工作负载。假设我们已经拥有一个基于原生kubernetes搭建起来的OpenYurt集群，且至少有两个节点。
 
-## UnitedDeployment用户手册
+## YurtAppSet用户手册
 
-### 创建UnitedDeployment
+### 创建YurtAppSet
 
-- 利用deployment template创建一个UnitedDeployment
+- 通过`yurtappset_test.yaml`创建一个YurtAppSet
 
-```shell
-$ cat <<EOF | kubectl apply -f -
+```yaml
 apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
+kind: YurtAppSet
 metadata:
   labels:
     controller-tools.k8s.io: "1.0"
-  name: ud-test
+  name: yas-test
 spec:
   selector:
     matchLabels:
-      app: ud-test
+      app: yas-test
   workloadTemplate:
     deploymentTemplate:
       metadata:
         labels:
-          app: ud-test
+          app: yas-test
       spec:
         template:
           metadata:
             labels:
-              app: ud-test
+              app: yas-test
           spec:
             containers:
               - name: nginx
@@ -64,16 +63,15 @@ spec:
         key: apps.openyurt.io/example
         operator: Exists
   revisionHistoryLimit: 5 
-EOF
 ```
 
-- 查看UnitedDeployment
+- 查看YurtAppSet
 
 ```shell
-$ kubectl get ud
+$ kubectl get yas
 
-NAME      READY   WORKLOADTEMPLATE   AGE
-ud-test   3       Deployment         120m
+NAME       READY   WORKLOADTEMPLATE   AGE
+yas-test   3       Deployment         43s
 ```
 
 ### 检查由yurt-app-manager组件创建的deployment
@@ -81,25 +79,25 @@ ud-test   3       Deployment         120m
 ```shell
 $ kubectl get deploy
 
-NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
-ud-test-beijing-fp58z    1/1     1            1           122m
-ud-test-hangzhou-xv454   2/2     2            2           122m
-$ kubectl get pod -l app=ud-test
+NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
+yas-test-beijing-k5st4    1/1     1            1           54s
+yas-test-hangzhou-2jkj5   2/2     2            2           54s
+$ kubectl get pod -l app=yas-test
 
-  NAME                                      READY   STATUS    RESTARTS   AGE
-ud-test-beijing-fp58z-787d5b6b54-g4jk6    1/1     Running   0          100m
-ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr   1/1     Running   0          124m
-ud-test-hangzhou-xv454-5cd9c4f6b5-gmbgp   1/1     Running   0          124m
+NAME                                       READY   STATUS    RESTARTS   AGE
+yas-test-beijing-k5st4-56bc98cc7d-h7h86    1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-8mvn8   1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-vx85t   1/1     Running   0          72s
 ```
 
 
 
-### 为UnitedDeployment添加patch功能
+### 为YurtAppSet添加patch功能
 
-- 在文件uniteddeployment_deployment_test.yaml中添加patch字段，如下所示，文件36到41行
+- 在文件yurtappset_test.yaml中添加patch字段，如下所示，文件36到41行
 
 ```shell
-$ kubectl get ud ud-test -o yaml
+$ kubectl get yas yas-test -o yaml
    
   topology:
     pools:
@@ -130,27 +128,27 @@ $ kubectl get ud ud-test -o yaml
   *** 
 ```
 
-- patch能够使得由UnitedDeployment创建的位于北京节点池的deployment和pod中nginx镜像版本为1.19.0，而其他地区的nginx镜像版本为1.19.3。
+- patch能够使得由YurtAppSet创建的位于北京节点池的deployment和pod中nginx镜像版本为1.19.0，而其他地区的nginx镜像版本为1.19.3。
 
 ```shell
-$ kubectl get deploy ud-test-beijing-fp58z -o yaml
+$ kubectl get deploy yas-test-beijing-k5st4 -o yaml
 
 containers:
   - image: nginx:1.19.0
-$ kubectl get deploy ud-test-hangzhou-xv454 -o yaml
+$ kubectl get deploy yas-test-hangzhou-2jkj5 -o yaml
 
 containers:
   - image: nginx:1.19.3
 ```
 
-- 删除后，所有由UnitedDeployment创建的pod又恢复使用相同的镜像nginx1.19.3
+- 删除后，所有由YurtAppSet创建的pod又恢复使用相同的镜像nginx1.19.3
 
 ```shell
-$ kubectl get pod ud-test-beijing-fp58z-787d5b6b54-g4jk6 -o yaml
+$ kubectl get pod yas-test-beijing-k5st4-974b6958c-t2kfn -o yaml
 
 containers:
   - image: nginx:1.19.3
-$ kubectl get pod ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr -o yaml
+$ kubectl get pod yas-test-hangzhou-2jkj5-64588c484b-8mvn8 -o yaml
 containers:
   - image: nginx:1.19.3
 ```
diff --git a/sidebars.js b/sidebars.js
index ccb7fcdae3..147ef7ee7b 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -83,7 +83,7 @@ module.exports = {
                 {
                     'Workload': [
                         'user-manuals/workload/node-pool-management',
-                        'user-manuals/workload/uniteddeployment',
+                        'user-manuals/workload/yurt-app-set',
                         'user-manuals/workload/yurt-app-daemon',
                     ]
                 },
diff --git a/versioned_docs/version-v0.7.0/user-manuals/workload/uniteddeployment.md b/versioned_docs/version-v0.7.0/user-manuals/workload/uniteddeployment.md
deleted file mode 100644
index 7072a431ff..0000000000
--- a/versioned_docs/version-v0.7.0/user-manuals/workload/uniteddeployment.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: UnitedDeployment
----
-
-
-
-
-在[上一篇文章](./node-pool-management.md) 中我们介绍了节点池的使用，主要是节点池的创建和管理，进一步，我们开发了基于节点池的应用单元化部署能力，提高用户的运维效率。
-
-在这篇文章中，我们将展示yurt-app-manager如何帮助用户管理工作负载。假设我们已经拥有一个基于原生kubernetes搭建起来的OpenYurt集群，且至少有两个节点。
-
-## UnitedDeployment用户手册
-
-### 创建UnitedDeployment
-
-- 利用deployment template创建一个UnitedDeployment
-
-```shell
-$ cat <<EOF | kubectl apply -f -
-apiVersion: apps.openyurt.io/v1alpha1
-kind: UnitedDeployment
-metadata:
-  labels:
-    controller-tools.k8s.io: "1.0"
-  name: ud-test
-spec:
-  selector:
-    matchLabels:
-      app: ud-test
-  workloadTemplate:
-    deploymentTemplate:
-      metadata:
-        labels:
-          app: ud-test
-      spec:
-        template:
-          metadata:
-            labels:
-              app: ud-test
-          spec:
-            containers:
-              - name: nginx
-                image: nginx:1.19.3
-  topology:
-    pools:
-    - name: beijing 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - beijing 
-      replicas: 1
-    - name: hangzhou 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - hangzhou 
-      replicas: 2
-      tolerations:
-      - effect: NoSchedule
-        key: apps.openyurt.io/example
-        operator: Exists
-  revisionHistoryLimit: 5 
-EOF
-```
-
-- 查看UnitedDeployment
-
-```shell
-$ kubectl get ud
-
-NAME      READY   WORKLOADTEMPLATE   AGE
-ud-test   3       Deployment         120m
-```
-
-### 检查由yurt-app-manager组件创建的deployment
-
-```shell
-$ kubectl get deploy
-
-NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
-ud-test-beijing-fp58z    1/1     1            1           122m
-ud-test-hangzhou-xv454   2/2     2            2           122m
-$ kubectl get pod -l app=ud-test
-
-  NAME                                      READY   STATUS    RESTARTS   AGE
-ud-test-beijing-fp58z-787d5b6b54-g4jk6    1/1     Running   0          100m
-ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr   1/1     Running   0          124m
-ud-test-hangzhou-xv454-5cd9c4f6b5-gmbgp   1/1     Running   0          124m
-```
-
-
-
-### 为UnitedDeployment添加patch功能
-
-- 在文件uniteddeployment_deployment_test.yaml中添加patch字段，如下所示，文件36到41行
-
-```shell
-$ kubectl get ud ud-test -o yaml
-   
-  topology:
-    pools:
-    - name: beijing 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - beijing 
-      replicas: 1
-      patch:
-        spec:
-          template:
-            spec:
-              containers:
-                - name: nginx
-                  image: nginx:1.19.0
-    - name: hangzhou 
-      nodeSelectorTerm:
-        matchExpressions:
-        - key: apps.openyurt.io/nodepool
-          operator: In
-          values:
-          - hangzhou 
-      replicas: 2
-      tolerations:
-  *** 
-```
-
-- patch能够使得由UnitedDeployment创建的位于北京节点池的deployment和pod中nginx镜像版本为1.19.0，而其他地区的nginx镜像版本为1.19.3。
-
-```shell
-$ kubectl get deploy ud-test-beijing-fp58z -o yaml
-
-containers:
-  - image: nginx:1.19.0
-$ kubectl get deploy ud-test-hangzhou-xv454 -o yaml
-
-containers:
-  - image: nginx:1.19.3
-```
-
-- 删除后，所有由UnitedDeployment创建的pod又恢复使用相同的镜像nginx1.19.3
-
-```shell
-$ kubectl get pod ud-test-beijing-fp58z-787d5b6b54-g4jk6 -o yaml
-
-containers:
-  - image: nginx:1.19.3
-$ kubectl get pod ud-test-hangzhou-xv454-5cd9c4f6b5-b5tsr -o yaml
-containers:
-  - image: nginx:1.19.3
-```
-
-- 结论：Patch功能解决了nodepool单属性的升级和应用完整发布。
-
diff --git a/versioned_docs/version-v0.7.0/user-manuals/workload/yurt-app-daemon.md b/versioned_docs/version-v0.7.0/user-manuals/workload/yurt-app-daemon.md
index f86a045ed6..fe8fc5036a 100644
--- a/versioned_docs/version-v0.7.0/user-manuals/workload/yurt-app-daemon.md
+++ b/versioned_docs/version-v0.7.0/user-manuals/workload/yurt-app-daemon.md
@@ -2,22 +2,19 @@
 title: YurtAppDaemon
 ---
 
-## 背景介绍
+## Background
 
-在边缘场景中，来自同一区域的边缘节点被分配到同一个节点池中，此时，一般需要在节点池维度部署一些系统组件，例如CoreDNS。 创建节点池时，我们希望自动创建这些系统组件，而无需任何手动操作。
-
-
-
-YurtAppDaemon 确保所有或部分节点池以 Deployment 或 StatefulSet 作为模板运行副本。 随着节点池的创建，这些子部署或状态集也被添加到集群中，子部署或状态集的创建/更新由 YurtAppDaemon 控制器实现。 这些子 Deployments 或 Statefulsets 将在节点池 从集群中移除时被回收，删除 YurtAppDaemon CR 将清理它创建的 Deployments 或 StatefulSets。 YurtAppDaemon 的行为类似于 K8S Daemonset，不同之处在于 YurtAppDaemon 从节点池维度自动创建 K8S 工作负载。
+In edge scenarios, edge nodes from the same region will be assigned to the same NodePool, at which point some system components, such as CoreDNS, will typically need to be deployed in NodePool dimension. When creating the NodePool, we want to create these system components automatically, without any manual operations.
 
+YurtAppDaemon ensures that all or some of the NodePools run replicas with a Deployment or StatefulSet template. As NodePools are created, these sub-Deployments or sub-StatefulSets are added to the cluster and the creation/updating of them are controlled by the YurtAppDaemon controller.
 
 
 
 ![img](https://intranetproxy.alipay.com/skylark/lark/0/2022/png/31456432/1641999454831-b8f2f9f4-c715-4063-8444-b0af22830092.png)
 
-## 用户使用：
+## Usage：
 
-- 创建test1节点池
+- Create test1 NodePool
 
 ```shell
 cat <<EOF | kubectl apply -f -
@@ -37,7 +34,7 @@ spec:
 EOF
 ```
 
-- 创建test2节点池
+- Create test2 NodePool
 
 ```shell
 cat <<EOF | kubectl apply -f -
@@ -55,7 +52,7 @@ spec:
 EOF
 ```
 
-- 将节点加入到节点池
+- Add nodes to the corresponding NodePool
 
 ```shell
  kubectl label node cn-beijing.172.23.142.31 apps.openyurt.io/desired-nodepool=test1
@@ -65,7 +62,7 @@ EOF
  kubectl label node cn-beijing.172.23.142.35 apps.openyurt.io/desired-nodepool=test2
 ```
 
-- 创建YurtAppDaemon
+- Create YurtAppDaemon
 
 ```shell
 cat <<EOF | kubectl apply -f -
@@ -106,7 +103,7 @@ spec:
 EOF
 ```
 
-- 为test1节点池打标签
+- Label test1 NodePool
 
 ```shell
 kubectl label np test1 yurtappdaemon.openyurt.io/type=nginx
@@ -119,7 +116,7 @@ kubectl get deployments.apps
 # Check the Pod
 ```
 
-- 为test2节点池打标签
+- Label test2 NodePool
 
 ```shell
 kubectl label np test2 yurtappdaemon.openyurt.io/type=nginx
@@ -132,7 +129,7 @@ kubectl get deployments.apps
 # Check the Pod
 ```
 
-- 改变YurtAppDaemon
+- Update YurtAppDaemon
 
 ```shell
 # Change yurtappdaemon workloadTemplate replicas to 2
@@ -142,7 +139,7 @@ kubectl get deployments.apps
 # Check the Pod
 ```
 
-- 移除节点池标签
+- Remove NodePool labels
 
 ```shell
 # Remove the nodepool test1 label
@@ -160,3 +157,231 @@ kubectl label np test2 yurtappdaemon.openyurt.io/type-
 # Check the Pod
 ```
 
+
+## Example for deploying coredns
+
+> Using `YurtAppDaemon`+`service topology` to solve dns resolution problems
+
+- Create NodePool
+```shell
+cat <<EOF | kubectl apply -f -
+
+
+apiVersion: apps.openyurt.io/v1alpha1
+kind: NodePool
+metadata:
+  name: hangzhou
+spec:
+  selector:
+    matchLabels:
+      apps.openyurt.io/nodepool: hangzhou
+  taints:
+    - effect: NoSchedule
+      key: node-role.openyurt.io/edge
+  type: Edge
+
+
+EOF
+```
+
+- Add label to NodePool
+
+```shell
+kubectl label np hangzhou yurtappdaemon.openyurt.io/type=coredns
+```
+
+- Deploy coredns
+
+```shell
+cat <<EOF | kubectl apply -f -
+
+
+apiVersion: apps.openyurt.io/v1alpha1
+kind: YurtAppDaemon
+metadata:
+  name: coredns
+  namespace: kube-system
+spec:
+  selector:
+    matchLabels:
+       k8s-app: kube-dns
+  workloadTemplate:
+    deploymentTemplate:
+      metadata:
+        labels:
+          k8s-app: kube-dns
+      spec:
+        replicas: 2
+        selector:
+          matchLabels:
+            k8s-app: kube-dns
+        template:
+          metadata:
+            labels:
+              k8s-app: kube-dns
+          spec:
+            volumes:
+            - name: config-volume
+              configMap:
+               name: coredns
+               items:
+               - key: Corefile
+                 path: Corefile
+                 name: coredns
+            dnsPolicy: Default
+            serviceAccount: coredns
+            serviceAccountName: coredns
+            containers:
+            - args:
+              - -conf
+              - /etc/coredns/Corefile
+              image: k8s.gcr.io/coredns:1.6.7
+              imagePullPolicy: IfNotPresent
+              name: coredns
+              resources:
+                limits:
+                  memory: 170Mi
+                requests:
+                  cpu: 100m
+                  memory: 70Mi
+              securityContext:
+                allowPrivilegeEscalation: false
+                capabilities:
+                  add:
+                  - NET_BIND_SERVICE
+                  drop:
+                  - all
+                readOnlyRootFilesystem: true        
+              livenessProbe:
+                failureThreshold: 5
+                httpGet:
+                  path: /health
+                  port: 8080
+                  scheme: HTTP
+                initialDelaySeconds: 60
+                periodSeconds: 10
+                successThreshold: 1
+                timeoutSeconds: 5  
+              volumeMounts:
+              - mountPath: /etc/coredns
+                name: config-volume
+                readOnly: true
+  nodepoolSelector:
+    matchLabels:
+      yurtappdaemon.openyurt.io/type: "coredns"
+
+---
+apiVersion: v1
+kind: Service
+metadata:
+  namespace: kube-system
+  annotations:
+    prometheus.io/port: "9153"
+    prometheus.io/scrape: "true"
+    openyurt.io/topologyKeys: openyurt.io/nodepool
+  labels:
+    k8s-app: kube-dns
+    kubernetes.io/cluster-service: "true"
+    kubernetes.io/name: KubeDNS
+  name: kube-dns
+spec:
+  clusterIP: __kubernetes-coredns-ip__  ##修改为kubernetes dns service ip
+  ports:
+  - name: dns
+    port: 53
+    protocol: UDP
+    targetPort: 53
+  - name: dns-tcp
+    port: 53
+    protocol: TCP
+    targetPort: 53
+  - name: metrics
+    port: 9153
+    protocol: TCP
+    targetPort: 9153
+  selector:
+    k8s-app: kube-dns
+  sessionAffinity: None
+  type: ClusterIP   
+---
+apiVersion: v1
+data:
+  Corefile: |
+    .:53 {
+        errors
+        health {
+           lameduck 5s
+        }
+        ready
+        kubernetes cluster.local in-addr.arpa ip6.arpa {
+           pods insecure
+           fallthrough in-addr.arpa ip6.arpa
+           ttl 30
+        }
+        prometheus :9153
+        forward . /etc/resolv.conf
+        cache 30
+        loop
+        reload
+        loadbalance
+    }
+kind: ConfigMap
+metadata:
+  name: coredns
+  namespace: kube-system
+---
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  name: coredns
+  namespace: kube-system
+  labels:
+      kubernetes.io/cluster-service: "true"
+      addonmanager.kubernetes.io/mode: Reconcile
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  labels:
+    kubernetes.io/bootstrapping: rbac-defaults
+    addonmanager.kubernetes.io/mode: Reconcile
+  name: system:coredns
+rules:
+- apiGroups:
+  - ""
+  resources:
+  - endpoints
+  - services
+  - pods
+  - namespaces
+  verbs:
+  - list
+  - watch
+- apiGroups:
+  - ""
+  resources:
+  - nodes
+  verbs:
+  - get
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  annotations:
+    rbac.authorization.kubernetes.io/autoupdate: "true"
+  labels:
+    kubernetes.io/bootstrapping: rbac-defaults
+    addonmanager.kubernetes.io/mode: EnsureExists
+  name: system:coredns
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: ClusterRole
+  name: system:coredns
+subjects:
+- kind: ServiceAccount
+  name: coredns
+  namespace: kube-system
+
+
+EOF
+``` 
diff --git a/versioned_docs/version-v0.7.0/user-manuals/workload/yurt-app-set.md b/versioned_docs/version-v0.7.0/user-manuals/workload/yurt-app-set.md
new file mode 100644
index 0000000000..f25358abd8
--- /dev/null
+++ b/versioned_docs/version-v0.7.0/user-manuals/workload/yurt-app-set.md
@@ -0,0 +1,154 @@
+---
+title: YurtAppSet
+---
+
+
+
+
+In [the previous article](./node-pool-management.md) we introduced the use of `NodePool`, mainly the creation and management of `NodePool`. 
+Further, we developed the ability to deploy applications unitized based on `NodePool` to improve the efficiency of users' operations.
+
+In this article, we will show how `yurt-app-manager` can help users manage their workload. Assume we already have an OpenYurt cluster built on 
+native kubernetes with at least two nodes.
+
+
+### 1) Create YurtAppSet
+
+- Create `YurtAppSet` by `yurtappset_test.yaml`
+
+```yaml
+apiVersion: apps.openyurt.io/v1alpha1
+kind: YurtAppSet
+metadata:
+  labels:
+    controller-tools.k8s.io: "1.0"
+  name: yas-test
+spec:
+  selector:
+    matchLabels:
+      app: yas-test
+  workloadTemplate:
+    deploymentTemplate:
+      metadata:
+        labels:
+          app: yas-test
+      spec:
+        template:
+          metadata:
+            labels:
+              app: yas-test
+          spec:
+            containers:
+              - name: nginx
+                image: nginx:1.19.3
+  topology:
+    pools:
+    - name: beijing 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - beijing 
+      replicas: 1
+    - name: hangzhou 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - hangzhou 
+      replicas: 2
+      tolerations:
+      - effect: NoSchedule
+        key: apps.openyurt.io/example
+        operator: Exists
+  revisionHistoryLimit: 5 
+```
+
+- Check `YurtAppSet`
+
+```shell
+$ kubectl get yas
+NAME       READY   WORKLOADTEMPLATE   AGE
+yas-test   3       Deployment         43s
+```
+
+
+### 2) Check the deployments created by yurt-app-manager
+
+```shell
+$ kubectl get deploy
+NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
+yas-test-beijing-k5st4    1/1     1            1           54s
+yas-test-hangzhou-2jkj5   2/2     2            2           54s
+
+$ kubectl get pod -l app=yas-test
+NAME                                       READY   STATUS    RESTARTS   AGE
+yas-test-beijing-k5st4-56bc98cc7d-h7h86    1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-8mvn8   1/1     Running   0          72s
+yas-test-hangzhou-2jkj5-64588c484b-vx85t   1/1     Running   0          72s
+```
+
+
+### 3) Add patch to YurtAppSet
+
+- Add the patch field to the file `yurtappset_test.yaml` as follows, lines 36 to 41 of the file
+
+```shell
+$ kubectl get yas yas-test -o yaml
+   
+  topology:
+    pools:
+    - name: beijing 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - beijing 
+      replicas: 1
+      patch:
+        spec:
+          template:
+            spec:
+              containers:
+                - name: nginx
+                  image: nginx:1.19.0
+    - name: hangzhou 
+      nodeSelectorTerm:
+        matchExpressions:
+        - key: apps.openyurt.io/nodepool
+          operator: In
+          values:
+          - hangzhou 
+      replicas: 2
+      tolerations:
+  *** 
+```
+
+- This updates the nginx image version to 1.19.0 in the deployments and pods in Beijing NodePool, while keeping the nginx image version at 1.19.3 for the other regions
+
+```shell
+$ kubectl get deploy yas-test-beijing-k5st4 -o yaml
+containers:
+  - image: nginx:1.19.0
+
+$ kubectl get deploy yas-test-hangzhou-2jkj5 -o yaml
+containers:
+  - image: nginx:1.19.3
+```
+
+- After removing the patch, all pods created by YurtAppSet revert back to nginx1.19.3
+
+```shell
+$ kubectl get pod yas-test-beijing-k5st4-974b6958c-t2kfn -o yaml
+containers:
+  - image: nginx:1.19.3
+
+$ kubectl get pod yas-test-hangzhou-2jkj5-64588c484b-8mvn8 -o yaml
+containers:
+  - image: nginx:1.19.3
+```
+
+- Conclusion: Patch solves the upgrade of the NodePool's single attribute and application release.
diff --git a/versioned_sidebars/version-v0.7.0-sidebars.json b/versioned_sidebars/version-v0.7.0-sidebars.json
index 1a3ad642e7..07cd39e32c 100644
--- a/versioned_sidebars/version-v0.7.0-sidebars.json
+++ b/versioned_sidebars/version-v0.7.0-sidebars.json
@@ -82,7 +82,7 @@
                 {
                     "Workload": [
                         "version-v0.7.0/user-manuals/workload/node-pool-management",
-                        "version-v0.7.0/user-manuals/workload/uniteddeployment",
+                        "version-v0.7.0/user-manuals/workload/yurt-app-set",
                         "version-v0.7.0/user-manuals/workload/yurt-app-daemon"
                     ]
                 },