diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
index 6f569a7..56cca80 100644
--- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
+++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
@@ -7,7 +7,7 @@
     - 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
-1. **A few mintues minutes later**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will make a selfie
+1. **A few minutes 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
     - Again, this short term memory churning causes µBlock's baseline memory footprint to grow further