diff --git a/documentation20/cn/03.architecture/docs.md b/documentation20/cn/03.architecture/docs.md
index d22855198abc804d6cee5603b56537c9315d610e..b481bea9f840ad459812f955aa76a8a7829d5b37 100644
--- a/documentation20/cn/03.architecture/docs.md
+++ b/documentation20/cn/03.architecture/docs.md
@@ -323,8 +323,6 @@ Vnode会保持一个数据版本号(Version)，对内存数据进行持久化存
 
 采用同步复制，系统的性能会有所下降，而且latency会增加。因为元数据要强一致，mnode之间的数据同步缺省就是采用的同步复制。
 
-注：vnode之间的同步复制仅仅企业版支持
-
 ## <a class="anchor" id="persistence"></a>缓存与持久化
 
 ### 缓存
diff --git a/documentation20/en/03.architecture/docs.md b/documentation20/en/03.architecture/docs.md
index 64696d79adc9a05672240caabf743a488a7507ae..ce8dd6c8be75ae87afcd51fbbecbaf97a274ba3e 100644
--- a/documentation20/en/03.architecture/docs.md
+++ b/documentation20/en/03.architecture/docs.md
@@ -322,8 +322,6 @@ For scenarios with higher data consistency requirements, asynchronous data repli
 
 With synchronous replication, performance of system will decrease and latency will increase. Because metadata needs strong consistent, the default for data synchronization between mnodes is synchronous replication.
 
-Note: synchronous replication between vnodes is only supported in Enterprise Edition
-
 ## <a class="anchor" id="persistence"></a> Caching and Persistence
 
 ### Caching