diff --git a/en/readme/distributed-scheduler.md b/en/readme/distributed-scheduler.md
index eef3ae0cc0f645ec4dd195d054fc572adf5560d2..ec46001bd381e1734384e13e8b2f7eb0d7536271 100755
--- a/en/readme/distributed-scheduler.md
+++ b/en/readme/distributed-scheduler.md
@@ -1,17 +1,25 @@
 # Distributed Scheduler<a name="EN-US_TOPIC_0000001115719369"></a>
 
 -   [Introduction](#section11660541593)
+-   [System Architecture](#section13587185873516)
 -   [Directory Structure](#section161941989596)
 -   [Repositories Involved](#section1371113476307)
 
 ## Introduction<a name="section11660541593"></a>
 
-The Distributed Scheduler in OpenHarmony provides functions related to system abilities \(also called system services\), including system ability startup, registration, and query.
+Distributed Scheduler is used for cross-device component management. It allows the local device to access or control remote components, and enables app collaboration in distributed scenarios. Its main functions are as follows:
 
-**Figure  1**  Distributed Scheduler subsystem architecture<a name="fig4460722185514"></a>  
+-   Remote ability startup: Starts an ability on a remote device.
+-   Remote ability migration: Migrates an ability to a remote device.
+-   Remote ability binding: Binds an ability on a remote device.
+-   System service management: Provides system service startup, registration, and query on the local device as well as system service query on a remote device.
 
+## System Architecture<a name="section13587185873516"></a>
 
-![](figures/en-us_image_0000001162500331.png)
+**Figure 1**  Distributed Scheduler architecture<a name="fig4460722185514"></a>
+
+
+![](figures/dms-architecture.png)
 
 ## Directory Structure<a name="section161941989596"></a>
 
diff --git a/en/readme/figures/dms-architecture.png b/en/readme/figures/dms-architecture.png
new file mode 100644
index 0000000000000000000000000000000000000000..1b7001cc23104148d5e6ea6b43cc32506872dc89
Binary files /dev/null and b/en/readme/figures/dms-architecture.png differ