diff --git a/Cloud-Drive-Architecture.md b/Cloud-Drive-Architecture.md
index ceffddc..6f3df1b 100644
--- a/Cloud-Drive-Architecture.md
+++ b/Cloud-Drive-Architecture.md
@@ -23,9 +23,13 @@ With this feature, SeaweedFS can cache data that is on cloud. It can cache both
 ![SeaweedFS Cloud Drive](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_RemoteMount.png)
 
 ```
-[HDFS|Mount|HTTP|S3|WebDAV] <== Filer(metadata cache) <== Volume Servers (data cache) <== Cloud
+[HDFS|Mount|HTTP|S3|WebDAV] <== Filer / Volume Server <== `remote.mount`           <== Cloud
+                                (metadata/data cache)      remote.meta.sync
+                                                           remote.cache
+                                                           remote.uncache
 
-[HDFS|Mount|HTTP|S3|WebDAV] ==> Filer(metadata cache) ==> Volume Servers (data cache) ==> `weed filer.remote.sync` ==> Cloud
+[HDFS|Mount|HTTP|S3|WebDAV] ==> Filer / Volume Server ==> `weed filer.remote.sync` ==> Cloud
+                                (metadata/data cache)
 ```
 
 There are no directory or file format changes to existing data on the cloud. So you do not need to change all existing workflows to read or write cloud files.