diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
index 6c33fb8..95f60ad 100644
--- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
+++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
@@ -6,7 +6,7 @@
 1. Once all filter lists are brought up to date, µBlock will flush from memory all filters and reload with the latest version
     - This will causes another round of short-term memory churning, which short-term memory will be garbage-collected eventually
     - Again, all this short term memory churning causes µBlock's baseline memory footprint to grow further
-    - You can disable auto-update if you want, but it is optimal to let µBlock take care of this
+    - You can disable auto-update if you want, but it is optimal to let µBlock take care of this, i.e. manually forcing an update is sub-optimal
 1. **A few minutes later**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will make a selfie
     - A selfie allows µBlock to skip the parsing/sorting of data next time it loads
     - Generating the selfie also causes short-term memory churning, which short-term memory will be garbage-collected eventually