diff --git a/Myth:-µBlock-consumes-over-80MB.md b/Myth:-µBlock-consumes-over-80MB.md
index 4729ac4..1ecda61 100644
--- a/Myth:-µBlock-consumes-over-80MB.md
+++ b/Myth:-µBlock-consumes-over-80MB.md
@@ -3,7 +3,7 @@ I've seen a couple of instances of people claiming µBlock is not as memory effi
 - ["I just installed it, and it uses 117MB - that's not even close"](http://www.reddit.com/r/chrome/comments/2cpogs/fast_and_light_ad_blocker_for_chrome_%C2%B5block/cjhutwz)
 - ["Simply tried, did not see where the province of memory" (Google translate...)](http://bbs.kafan.cn/thread-1762885-1-1.html#pid32323303)
 
-When µBlock launches, it loads all selected filter lists, parse the content, eliminate duplicates, then instantiates the filters using efficient internal representation. This parsing of the filter lists requires a good amount of temporary memory.
+When µBlock launches, it loads all selected filter lists, parses the content, eliminates duplicates, then instantiates the filters using efficient internal representation. This parsing of the filter lists requires a good amount of temporary memory.
 
 So if you look at the task manager **right after** µBlock has loaded and parsed the filter lists, you will still see µBlock's memory footprint as a result of loading all the filter lists. Still, at this point all this temporary memory has been relinquished to the browser, but the browser hasn't yet collected the freed memory to make it available for reuse.