diff --git a/Filer-Metadata-Events.md b/Filer-Metadata-Events.md
index 1d83c0a..dd33dd6 100644
--- a/Filer-Metadata-Events.md
+++ b/Filer-Metadata-Events.md
@@ -81,10 +81,11 @@ The `SubscribeMetadataResponse` contains `EventNotification`, which contains `ol
 * Update Event: `old_entry` is not null, and `new_entry` is not null.
 * Rename Event: similar to Update Event, but also need `SubscribeMetadataResponse.directory` and `EventNotification.new_parent_path`.
 
-## Purging Metadata
-It is safe to delete the metadata files for now. However, future development will rely on these metadata events to implement new features, such as:
-* Async filer replication (to replace existing dependency on other message queue, e.g., Kafka)
-* Recover deleted files
-* Snapshot
+## Purging Metadata Logs
+It is ok to delete the metadata logs. However, many features rely on these metadata events, such as:
+* Async filer replication
+* Sync metadata with `weed mount`
+* Async filer metadata backup
+* Filer backup
 
-The metadata should not take too much space. Just leave it there.
+So better not to mess with the metadata logs, which should not take too much space. Just leave them there.