diff --git a/Filer-as-a-Key-Large-Value-Store.md b/Filer-as-a-Key-Large-Value-Store.md
index 2b09f8f..61568f8 100644
--- a/Filer-as-a-Key-Large-Value-Store.md
+++ b/Filer-as-a-Key-Large-Value-Store.md
@@ -13,8 +13,8 @@ With SeaweedFS, a large value can be stored as a chunk on volume servers and can
 ## How to do it?
 
 There are two tricks:
-* Configure for [[Super Large Directories]]. It will avoid the additional work to maintain the file list in the large folder.
-* Optionally configure to store small values in filer store. E.g., `weed filer -saveToFilerLimit=1024` will store values less than 1KB to filer store itself. Accessing these entries are basically no difference than accessing the underlying key-value stores directly.
+* Usually the entries are in one folder. You can configure for [[Super Large Directories]]. It will avoid the additional work to maintain the file list in the large folder.
+* Optionally configure to store small values in filer store. E.g., `weed filer -saveToFilerLimit=1024` will store values less than 1KB to filer store itself. Accessing these small entries are basically no difference than accessing the underlying key-value stores directly.
 
 ## AWS S3 is a poor key-value store