Update 4.storage-service.md (#2011)

docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md

@@ -247,16 +247,16 @@ When a transfer leadership command is committed, the leader will abandon its lea
 
 To avoid split-brain, when members in a Raft Group change, an intermediate state is required. In such a state, the quorum of the old group and new group always have an overlap. Thus it prevents the old or new group from making decisions unilaterally. To make it even simpler, in his doctoral thesis Diego Ongaro suggests adding or removing a peer once to ensure the overlap between the quorum of the new group and the old group. NebulaGraph also uses this approach, except that the way to add or remove a member is different. For details, please refer to addPeer/removePeer in the Raft Part class.
 
-<!-- open after fully tested
-{{ent.ent_begin}}
+<!-- open after fully tested, add macro since it is an enterprise feature
+
 
 ## Cache
 
 The cache management of RocksDB can not cache vertices or edges on demand. NebulaGraph implements its own cache management for Storage, allowing you to set the storage cache size, content, etc. For more information, see [Storage cache configurations](../../5.configurations-and-logs/1.configurations/4.storage-config.md).
 
 You can query the cache stats through the cURL command `curl "http://[storaged IP]:[http port]/cache?stats"`.
 
-{{ent.ent_end}} -->
+-->
 
 ## Differences with HDFS