diff --git a/README.md b/README.md
index 4a5d6770de06b6fc7a54be9c935328b992b360d1..0e984ba6c7a13a6977a136a071fe51ceb709030c 100644
--- a/README.md
+++ b/README.md
@@ -58,8 +58,9 @@ The manual way of installing and setting up lektor:
 
 ```sh
 cmake -Bbuild \
-    -DCMAKE_C_COMPILER=clang \ # Choose the compiler
-    -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE=Debug # The debug stuff
+    -DCMAKE_C_COMPILER=clang           \ # Choose the compiler
+    -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \ # For clangd/ccls
+    -DCMAKE_BUILD_TYPE=Debug             # The debug stuff
 ```
 
 Note that the last option is here to generate the `compile_commands.json`, you
@@ -68,7 +69,9 @@ should copy it at the root of the project.
 The sqlite database and the config file will be created automatically if needed,
 i.e. on the first run. If you are upgrading lektor, the config might not be
 correct. You can delete the config file or use the `lkt admin config` to
-generate the config file again.
+generate the config file again. If you are using special modules or are
+compiling lektor without static modules, you may set their **absolute path**
+inside the lektor's config file.
 
 > **Important note**: Upgrading the config or the database scheme automatically
 is not supported yet. If you are experiencing weird things with lektord, please
@@ -76,9 +79,6 @@ try first to delete the database and config and regenerate them. There are
 currently no way of doing a backup of playlists and stickers with lektor, this
 is WIP.
 
-If you are using special modules or are compiling lektor without static modules,
-you may set their **absolute path** inside the lektor's config file.
-
 ## Preparing a kara for lektor
 
 The ideal way of populating lektor is using *Kurisu*. The `update` is here for
@@ -92,15 +92,12 @@ command.
 To run lektor, you can simply run the binary like: `./lektord`. If lektord did
 not exited normally (i.e. without the `lkt adm kill` command), the database will
 still store the fact that lektord is running. To by-pass it, you will need to
-launch lektord with the `-F` (forced) option, like `lektord -F`.
-
-It is not recommended to launch always lektord with the `-F` option, because
-that way you could launch multiple instances of the lektod daemon, which could
-results in undefined behaviours.
-
-Lektor will use specialized software (hwdec set to yes), if you have an nvidia
-card with optimus (in almose every laptop), please use `optirun` or `primusrun`:
-`optirun ./lektord`
+launch lektord with the `-F` (forced) option, like `lektord -F`. It is not
+recommended to launch always lektord with the `-F` option, because that way you
+could launch multiple instances of the lektod daemon, which could results in
+undefined behaviours. Lektor will use specialized software (hwdec set to yes),
+if you have an nvidia card with optimus (in almose every laptop), please use
+`optirun` or `primusrun`: `optirun ./lektord`
 
 ### How to update the lektord database