diff --git a/manual/config/seafile-conf.md b/manual/config/seafile-conf.md
index 1004252c..bbcf5609 100644
--- a/manual/config/seafile-conf.md
+++ b/manual/config/seafile-conf.md
@@ -142,6 +142,16 @@ max_sync_file_count = 100000
 fs_id_list_request_timeout = 300
 ```
 
+New in Seafile Pro 8.0.5: If you use cloud storage backend, you can enable the `use_block_cache` configuration to speed up file access. `use_block_cache` the default value is false. Note that this configuration is only effective for downloading files through web page or API, not for synchronized files. The `block_cache_size_limit` configuration is used to limit the size of the cache. `block_cache_size_limit` the default value is 10GB. the `block_cache_file_types` configuration is used to limit the file types that are cached. `block_cache_file_types` the default value is mp4;mov.
+
+```
+[fileserver]
+use_block_cache = true
+# Set block cache size limit to 100MB
+block_cache_size_limit = 100
+block_cache_file_types = mp4;mov
+```
+
 ## Database configuration
 
 The whole database configuration is stored in the `[database]` section of the configuration file, whether you use SQLite, MySQL or PostgreSQL.
diff --git a/manual/maintain/seafile_gc.md b/manual/maintain/seafile_gc.md
index 4613a44d..822b6cb7 100644
--- a/manual/maintain/seafile_gc.md
+++ b/manual/maintain/seafile_gc.md
@@ -92,6 +92,15 @@ seaf-gc.sh -r
 
 **In Seafile version 4.1.1 and later, libraries deleted by the users are not immediately removed from the system. Instead, they're moved into a "trash" in the system admin page. Before they're cleared from the trash, their blocks won't be garbage collected.**
 
+### Removing FS objects
+
+Since Pro server 8.0.6, you can remove garbage fs objects. It should be run without the --dry-run option:
+
+```
+seaf-gc.sh --rm-fs
+
+```
+
 ### Using Multiple Threads in GC
 
 Since Pro server 5.1.0, you can specify the thread number in GC. By default,