From 4957442abd38d2a61b850157ad80071fd8484422 Mon Sep 17 00:00:00 2001
From: Lee Watson <lee.watson@netgo.de>
Date: Thu, 27 Feb 2025 13:38:20 +0000
Subject: [PATCH] notes from Bas

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 6907f94..771dd3a 100644
--- a/README.md
+++ b/README.md
@@ -9,12 +9,12 @@ Roles:
 
 * New User: new key to be added; can be a new employee being added for first time, existing employee getting access to a new repo, key rotation, etc
 * Existing User: user who already has access to the appropriate project
-  * E.g. look up in the [groups](/groups/) dir
+  * E.g. look up in the [groups](/groups/) dir    <!-- Review from Bas: The "e.g." is a bit confusing to me. Did you mean "i.e." instead? I'm OK if you leave the "e.g." out. -->
   * 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_<firstname>-<lastname>` <!-- Review from Bas: Please make sure it's clear to the user that you mean this repo. -->
-  - e.g. `git branch add_pubkey_test-user`   <!-- Review from Bas: The "e.g." is a bit confusing to me. Did you mean "i.e." instead? I'm OK if you leave the "e.g." out. -->
+  - 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