diff --git a/docs/en/Example_Delay.md b/docs/en/Example_Delay.md
index 80785256d9e7033d87eb27b8f9820b6acdc45673..fe41aed92bacb40c30b6c62811a4e07d954f50b6 100644
--- a/docs/en/Example_Delay.md
+++ b/docs/en/Example_Delay.md
@@ -1,6 +1,6 @@
 # Schedule example
 
-### 1.Start consumer to wait for incoming subscribed messages 
+### 1 Start consumer to wait for incoming subscribed messages 
 
 ```java
 import org.apache.rocketmq.client.consumer.DefaultMQPushConsumer;
@@ -35,7 +35,7 @@ public class ScheduledMessageConsumer {
 }
 ```
 
-### 2.Send scheduled messages 
+### 2 Send scheduled messages 
 
 ```java
 import org.apache.rocketmq.client.producer.DefaultMQProducer;
@@ -64,15 +64,15 @@ public class ScheduledMessageProducer {
 }
 ```
 
-### 3.Verification 
+### 3 Verification 
 
 You should see messages are consumed about 10 seconds later than their storing time. 
 
-### 4.Use scenarios for scheduled messages
+### 4 Use scenarios for scheduled messages
 
 For example, in e-commerce, if an order is submitted, a delay message can be sent, and the status of the order can be checked after 1 hour. If the order is still unpaid, the order can be cancelled and the inventory released.
 
-### 5.Restrictions on the use of scheduled messages
+### 5 Restrictions on the use of scheduled messages
 
 ```java 
 // org/apache/rocketmq/store/config/MessageStoreConfig.java
@@ -82,4 +82,4 @@ private String messageDelayLevel = "1s 5s 10s 30s 1m 2m 3m 4m 5m 6m 7m 8m 9m 10m
 
 Nowadays RocketMq does not support any time delay. It needs to set several fixed delay levels, which correspond to level 1 to 18 from 1s to 2h. Message consumption failure will enter the delay message queue. Message sending time is related to the set delay level and the number of retries.
 
- See `SendMessageProcessor.java` 
\ No newline at end of file
+ See `SendMessageProcessor.java`