diff --git a/README.md b/README.md index 173d7ad..7c2e00e 100644 --- a/README.md +++ b/README.md @@ -13,8 +13,8 @@ Roles: * E.g. look up in in [verify/.sops.yaml](verify/.sops.yaml) ## 1a. Onboarding: [New User]: create and add a gpg key -- create a branch titled `add_pubkey_-` - - e.g. `git branch add_pubkey_test-user` +- create a branch titled `add_pubkey_-` + - e.g. `git branch add_pubkey_test-user` - Note: no strict naming convention for the branch, it's strictly a Human-in-the-Loop process - please 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 @@ -22,7 +22,7 @@ Roles: - file format: `@netgo.de.gpg.pub` - git: commit the new file, push - open a MergeRequest/PullRequest -- hand-off to an Existing User of the repo. +- hand-off to an Existing User of the repo. ## 1b. Onboarding: [Existing User|New User]: Add new user to groups @@ -35,7 +35,7 @@ cd groups/ ln -s ../../ ``` -Note: this step can be performed by anyone (either new user or existing user), but it makes the most sense for an existing user to configure the groups since this is domain-specific knowledge (i.e. new users won't typically know the grups) +Note: this step can be performed by anyone (either new user or existing user), but it makes the most sense for an existing user to configure the groups since this is domain-specific knowledge (i.e. new users won't typically know the grups) ## 3. Onboarding: [Existing User]: Configure sops config