diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
index 4091551..6c13f85 100644
--- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
+++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md
@@ -1,11 +1,11 @@
 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 lists need to be updated
+1. **Five minutes later**, µ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
-1. After **seven minutes**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will make a selfie
+1. **Seven 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