diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
index ac92619..4420ec2 100644
--- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
+++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
@@ -1,7 +1,7 @@
 1. µBlock will load the default selection of filter lists:
     - This causes short-term memory churning (loading/parsing/sorting/storing), which short-term memory will be garbage-collected eventually
     - All this short term memory churning causes µBlock's baseline memory footprint to grow further
-1. After **five minutes**, µBlock will look whether one or more filter list need to be updated
+1. After **five minutes**, µBlock will look whether one or more filter lists need to be updated
 1. If an update is needed, µ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