diff --git a/Remote-Storage-Architecture.md b/Remote-Storage-Architecture.md
index a46f859..f91f8e1 100644
--- a/Remote-Storage-Architecture.md
+++ b/Remote-Storage-Architecture.md
@@ -69,3 +69,8 @@ The asynchronous write back will not slow down any local operations.
 * Saving data files. With cloud capacity and storage tiering, saving data files there may be a good idea. The cache can save the programming effort.
 * Multiple access methods, HDFS/HTTP/S3/WebDav/Mount, to access remote storage. No need to use one specific way to access remote storage.
 * If you plan to move off cloud, you can start with SeaweedFS Remote Storage Cache. When you are happy with it, just stop the write back process (and cancel the monthly payment to the cloud vendor!).
+
+# Continue to read
+  * [[Configure Remote Storage]]
+  * [[Mount Remote Storage]]
+  * [[Cache Remote Storage]]