From b8853f660971d7e3a6aaabb9fc9ef06165127d0e Mon Sep 17 00:00:00 2001
From: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com>
Date: Fri, 25 Mar 2022 11:32:15 +0800
Subject: [PATCH] Update
 docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>
---
 .../3.nebula-graph-architecture/4.storage-service.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md
index beef47bfc41..2b47afa18a5 100644
--- a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md
+++ b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md
@@ -250,7 +250,7 @@ To avoid split-brain, when members in a Raft Group change, an intermediate state
 
 ## Cache
 
-The cache management of RocksDB can not caching vertex or edge as required, Nebula Graph implemented storage cache management itself, users can set the storage cache size, content, etc. For more information, see [Storage cache configurations](../../5.configurations-and-logs/1.configurations/4.storage-config.md).
+The cache management of RocksDB can not cache vertices or edges on demand. Nebula Graph 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).
 
 ## Differences with HDFS