docs: format

README.md

@@ -49,7 +49,6 @@ Make sure to utilize the github search if you know what you need!
 
   By convention I place secrets related to this host in the `secrets/` subfolder, but any host
   could technically use them. Especialy important files in this folder are:
-
   - `host.pub` This host's public key (retrieved after initial setup). Used to rekey secrets so the host can access them at runtime.
   - `local.nix.age` Repository-wide local secrets. Decrypted on import, see `modules/repo/secrets.nix` for more information.
 
@@ -62,21 +61,16 @@ Make sure to utilize the github search if you know what you need!
   my configuration, this is probably the folder you are looking for. Unless stated otherwise,
   all of these will be regular reusable modules like those you would find in `nixpkgs/nixos/modules`,
   and the tree of all relevant modules is included via `modules/default.nix`.
-
   - `modules/config/` contains configuration that is I use across all my host and is applied by default.
     These just add configuration unconditionally and don't expose any further options.
-
   - `modules/optional/` contains configuration that is only needed sometimes, and which should
     be included explicitly by hosts that require it.
-
   - `modules/meta/` contains meta-modules that simplify the option interface of existing options.
     I use this for stuff that I don't need on all my hosts and that may require different settings
     for each host while sharing a common basis.
-
     Some of these are "meta" in the sense that they depend on their own definitions on multiple hosts (wireguard).
     These are probably as opinionated as stuff in `modules/config/` but may be a little more general.
     The `wireguard` module would even be a candidate for extraction to a separate flake, together with the related apps.
-
   - `modules/<xyz>/` regular modules related to <xyz>, similar structure as in `nixpkgs/nixos/modules`
 
 - `nix/` library functions and flake plumbing