diff --git a/Notes on memory benchmarks, selfies.md b/Notes-on-memory-benchmarks,-selfies.md
similarity index 91%
rename from Notes on memory benchmarks, selfies.md
rename to Notes-on-memory-benchmarks,-selfies.md
index f0cd186..a71a407 100644
--- a/Notes on memory benchmarks, selfies.md	
+++ b/Notes-on-memory-benchmarks,-selfies.md
@@ -13,7 +13,7 @@ Reloading all the filters is the most severe memory-churning operation in µBloc
 - Adding removing custom filters.
 - Updating the filter lists (this may be done automatically if _Auto-update_ is enabled).
 
-Additionally, with version 0.6+, µBlock is able to create a selfie to improve its load time next time the browser is launched, and creating a selfie is also a memory-churning operation. However for this one particular operation, once the selfie is created, the reward is that subsequent re-launch of µBlock will become very efficient CPU- and memory-wise -- as all the downloading/parsing of filters from raw text files will be completely bypassed.
+Additionally, with version 0.6+, µBlock is able to create a selfie to improve its load time next time the browser is launched, and creating a selfie is also a memory-churning operation. However for this one particular operation, once the selfie is created, the reward is that subsequent launch of µBlock will become very efficient CPU- and memory-wise -- as all the downloading/parsing of filters from raw text files will be completely bypassed.
 
 The time at which a selfie is created is at µBlock's discretion. Currently, this will happen some minutes after the filter lists has been loaded, so as to avoid launching memory-churning selfie creation operations before there is a good likelihood the user is done tampering with his selection of filters.