diff --git a/docs/en/Deployment.md b/docs/en/Deployment.md
index b0a27327fbe4082c6b43a90293a6b66e06e5845c..eadfec53d5a0641bd9d041aaa703deacbc79a85b 100644
--- a/docs/en/Deployment.md
+++ b/docs/en/Deployment.md
@@ -1,8 +1,10 @@
-# Installation Guides
+# Deployment Architectures and Setup Steps
+
+## Cluster Setup
 
 ### 1 Single Master mode
 
-This is the simplest but also the riskiest mode, that makes the entire service unavailable once the broker restarts or goes down. Production environments are not recommended, but can be used for local testing and development. Here are the steps to build.
+This is the simplest, but also the riskiest mode, that makes the entire service unavailable once the broker restarts or goes down. Production environments are not recommended, but can be used for local testing and development. Here are the steps to build.
 
 **1）Start NameServer**
 
@@ -67,7 +69,7 @@ $ nohup sh mqbroker -n 192.168.1.1:9876 -c $ROCKETMQ_HOME/conf/2m-noslave/broker
 ...
 ```
 
-The boot command shown above is used in the case of a single NameServer. For clusters of multiple NameServer, the address list after the -n argument in the broker boot command is separated by semicolons, for example, 192.168.1.1: 9876;192.161.2: 9876.
+The boot command shown above is used in the case of a single NameServer.For clusters of multiple NameServer, the address list after the -n argument in the broker boot command is separated by semicolons, for example, 192.168.1.1: 9876;192.161.2: 9876.
 
 ### 3 Multiple Master And Multiple Slave Mode-Asynchronous replication