From a857d242f09a429f38f9594979716f31f0c2f174 Mon Sep 17 00:00:00 2001
From: gitdh <42263983+gitdh@users.noreply.github.com>
Date: Fri, 1 Mar 2019 15:53:27 +0800
Subject: [PATCH] [RIP-9]

Add the introduction of the terminology in RocketMQ
---
 docs/en/Design_Store.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/Design_Store.md b/docs/en/Design_Store.md
index ac140223..9645c3fd 100644
--- a/docs/en/Design_Store.md
+++ b/docs/en/Design_Store.md
@@ -33,4 +33,4 @@ In addition, RocketMQ mainly reads and writes files through `MappedByteBuffer`.
 
 
 * synchronous flush: As shown above, the RocketMQ's Broker will return a successful `ACK` response to the Producer after the message is truly persisted to disk. Synchronous flushing is a good guarantee for the reliability of MQ messages, but it will have a big impact on performance. Generally, it is suitable for financial business applications.
-* asynchronous flush: Asynchronous flushing can take full advantage of the PageCache of the OS, as long as the message is written to the PageCache, the successful `ACK` can be returned to the Producer. The message flushing is performed by the background asynchronous thread, which reduces the read and write delay and improves the performance and throughput of the MQ.
\ No newline at end of file
+* asynchronous flush: Asynchronous flushing can take full advantage of the PageCache of the OS, as long as the message is written to the PageCache, the successful `ACK` can be returned to the Producer. The message flushing is performed by the background asynchronous thread, which reduces the read and write delay and improves the performance and throughput of the MQ. 
-- 
GitLab