diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
index 4420ec2..97ffe32 100644
--- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
+++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
@@ -11,5 +11,5 @@
     - Any change in the selection of filter lists, or change in the content of selected filter lists will invalidate µBlock's selfie
 1. Even after the growth in memory baseline, µBlock's own memory footprint is still quite smaller than that of Adblock Plus.
 1. µBlock's much smaller contributed memory footprint to web pages is much smaller than that of ABP
-    - Though this measure is less visible, it's where you get the biggest bang for the buck with µBlock relative to ABP.
-
+    - As opposed to µBlock's own memory footprint, visible using Chromium's _"Task Manager"_, the contributed memory footprint cannot be seen by users
+    - Though this measure is not visible, it's where you get the biggest bang for the buck with µBlock relative to ABP -- because µBlock **does not** inject thousands of CSS rules into pages and embedded frames.
\ No newline at end of file