diff --git a/README.md b/README.md
index 1a0144a..5d3fe0e 100644
--- a/README.md
+++ b/README.md
@@ -13,18 +13,17 @@ Roles:
 
 ## 1a. Onboarding: [New User]: create and add a gpg key
 1. Clone this repository
-1. Create a branch titled `add_pubkey_[firstname]-[lastname]`. <!-- NOTE: Validation Hack: User will not be able to mistakenly create this literal branch, as the unpermitted chars '[' will prevent the branch from being created: "Branch name cannot contain '['" as per https://git-scm.com/docs/git-check-ref-format. I.e. it's a dirty hack to get some server-side(?) validation ;-) --> 
-<!--  - Web: e.g. The following link can be used to create a branch: [https://git.dev-at.de/smardigo-hetzner/communication-keys/-/branches/new?branch_name=add_pubkey_[firstname]-[lastname]](https://git.dev-at.de/smardigo-hetzner/communication-keys/-/branches/new?branch_name=add_pubkey_[firstname]-[lastname]) -->
-  - CLI: e.g. `git branch add_pubkey_Max-Musterman`
-  - Note: no strict naming convention for the branch, it's strictly a Human-in-the-Loop process
+1. Create a branch titled `add_pubkey_[firstname]-[lastname]`. <!-- NOTE: Validation Hack: User will not be able to mistakenly create this literal branch, as the unpermitted chars '[' will prevent the branch from being created: "Branch name cannot contain '['" as per https://git-scm.com/docs/git-check-ref-format. I.e. it's a dirty hack to get some server-side(?) validation ;-) --> <!--  - Web: e.g. The following link can be used to create a branch: [https://git.dev-at.de/smardigo-hetzner/communication-keys/-/branches/new?branch_name=add_pubkey_[firstname]-[lastname]](https://git.dev-at.de/smardigo-hetzner/communication-keys/-/branches/new?branch_name=add_pubkey_[firstname]-[lastname]) -->
+    - CLI: e.g. `git branch add_pubkey_Max-Musterman`
+    - Note: no strict naming convention for the branch, it's strictly a Human-in-the-Loop process
 1. Follow steps 1-13 at the following link: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
-  - CAVEAT: step 14 is not necessary, as it is specific to a GitHub account
+    - CAVEAT: step 14 is not necessary, as it is specific to a GitHub account
 1. add ONLY the _PUBLIC_ part of your gpg key!!! to your branch
-  - file format: `<email>@netgo.de.gpg.pub`
+    - file format: `<email>@netgo.de.gpg.pub`
 1. git: commit the new file, push
 1. open a MergeRequest
 1. Hand-Off: Assign the MR to an Existing User in your Team to have your key added.
-   1. Hint: Look up all Existing Users in the comments at: [verify/.sops.yaml](verify/.sops.yaml)
+    - Hint: Look up all Existing Users in the comments at: [verify/.sops.yaml](verify/.sops.yaml)
 
 ## 1b. Onboarding: [Existing User|New User]: Add new user to groups