5 files changed, 48 insertions, 37 deletions
diff --git a/notes/git_crypt.md b/notes/git_crypt.md
index 6b2cb765..4e192a89 100644
--- a/notes/git_crypt.md
+++ b/notes/git_crypt.md
@@ -1,6 +1,7 @@
 # what to do, when nix wants to build the locked repository
 
 Simply delete the source path:
+
 ```
 sudo nix store delete --ignore-liveness <source_path>
 ```
diff --git a/notes/gpg_keys.md b/notes/gpg_keys.md
index c77a6bde..39602e3b 100644
--- a/notes/gpg_keys.md
+++ b/notes/gpg_keys.md
@@ -1,45 +1,48 @@
 # How to add a comment to gpg keys
+
 Export it as follows:
+
 ```bash
 gpg --export --armor --comment '<keyid>' <add comments for every line in ` gpg -k`> <key_name> > key_out.gpg
 ```
+
 or add it manually, the supported options include (RFC4880):
 
- - "Version", which states the OpenPGP implementation and version
-   used to encode the message.
+- "Version", which states the OpenPGP implementation and version
+  used to encode the message.
 
- - "Comment", a user-defined comment.  OpenPGP defines all text to
-   be in UTF-8.  A comment may be any UTF-8 string.  However, the
-   whole point of armoring is to provide seven-bit-clean data.
-   Consequently, if a comment has characters that are outside the
-   US-ASCII range of UTF, they may very well not survive transport.
+- "Comment", a user-defined comment.  OpenPGP defines all text to
+  be in UTF-8.  A comment may be any UTF-8 string.  However, the
+  whole point of armoring is to provide seven-bit-clean data.
+  Consequently, if a comment has characters that are outside the
+  US-ASCII range of UTF, they may very well not survive transport.
 
- - "MessageID", a 32-character string of printable characters.  The
-   string must be the same for all parts of a multi-part message
-   that uses the "PART X" Armor Header.  MessageID strings should be
-   unique enough that the recipient of the mail can associate all
-   the parts of a message with each other.  A good checksum or
-   cryptographic hash function is sufficient.
+- "MessageID", a 32-character string of printable characters.  The
+  string must be the same for all parts of a multi-part message
+  that uses the "PART X" Armor Header.  MessageID strings should be
+  unique enough that the recipient of the mail can associate all
+  the parts of a message with each other.  A good checksum or
+  cryptographic hash function is sufficient.
 
-   The MessageID SHOULD NOT appear unless it is in a multi-part
-   message.  If it appears at all, it MUST be computed from the
-   finished (encrypted, signed, etc.) message in a deterministic
-   fashion, rather than contain a purely random value.  This is to
-   allow the legitimate recipient to determine that the MessageID
-   cannot serve as a covert means of leaking cryptographic key
-   information.
+  The MessageID SHOULD NOT appear unless it is in a multi-part
+  message.  If it appears at all, it MUST be computed from the
+  finished (encrypted, signed, etc.) message in a deterministic
+  fashion, rather than contain a purely random value.  This is to
+  allow the legitimate recipient to determine that the MessageID
+  cannot serve as a covert means of leaking cryptographic key
+  information.
 
- - "Hash", a comma-separated list of hash algorithms used in this
-   message.  This is used only in cleartext signed messages.
+- "Hash", a comma-separated list of hash algorithms used in this
+  message.  This is used only in cleartext signed messages.
 
- - "Charset", a description of the character set that the plaintext
-   is in.  Please note that OpenPGP defines text to be in UTF-8.  An
-   implementation will get best results by translating into and out
-   of UTF-8.  However, there are many instances where this is easier
-   said than done.  Also, there are communities of users who have no
-   need for UTF-8 because they are all happy with a character set
-   like ISO Latin-5 or a Japanese character set.  In such instances,
-   an implementation MAY override the UTF-8 default by using this
-   header key.  An implementation MAY implement this key and any
-   translations it cares to; an implementation MAY ignore it and
-   assume all text is UTF-8.
+- "Charset", a description of the character set that the plaintext
+  is in.  Please note that OpenPGP defines text to be in UTF-8.  An
+  implementation will get best results by translating into and out
+  of UTF-8.  However, there are many instances where this is easier
+  said than done.  Also, there are communities of users who have no
+  need for UTF-8 because they are all happy with a character set
+  like ISO Latin-5 or a Japanese character set.  In such instances,
+  an implementation MAY override the UTF-8 default by using this
+  header key.  An implementation MAY implement this key and any
+  translations it cares to; an implementation MAY ignore it and
+  assume all text is UTF-8.
diff --git a/notes/laptop.md b/notes/laptop.md
index 9f809e30..38ae5a24 100644
--- a/notes/laptop.md
+++ b/notes/laptop.md
@@ -1,8 +1,12 @@
 # backlight
+
 Run `ls /sys/class/backlight` to see possible options.
 
 # brightness
-    #! / bin / bash
-    brightness = $ (cat / sys / class / backlight / intel_backlight / brightness)
-    brightness = $ (expr $ brightness - 300)
-    echo $ brightness> / sys / class / backlight / intel_backlight / brightness
+
+```
+#! / bin / bash
+brightness = $ (cat / sys / class / backlight / intel_backlight / brightness)
+brightness = $ (expr $ brightness - 300)
+echo $ brightness> / sys / class / backlight / intel_backlight / brightness
+```
diff --git a/notes/names.md b/notes/names.md
index 53eefe1c..44339580 100644
--- a/notes/names.md
+++ b/notes/names.md
@@ -1,4 +1,6 @@
 # Naming scheme
+
 The hosts naming scheme follows two list of Mesopotamian (Babylonian) deities:
+
 - https://en.wikipedia.org/wiki/List_of_Mesopotamian_deities
 - https://namingschemes.com/Babylonian_Gods
diff --git a/notes/password.md b/notes/password.md
index ff79aa38..96366bae 100644
--- a/notes/password.md
+++ b/notes/password.md
@@ -1,2 +1,3 @@
 # Password
+
 Run `nix run n#mkpasswd -- -m yescrypt -s -R 11`