some tweaks to git post

src/posts/2026/2026-01-07-intro-to-git.md

@@ -436,7 +436,7 @@ running `ssh-keygen` will take us through a series of prompts. Assuming we don't
 
 when you choose a passphrase, *write it down*. If you lose it, there is no recourse. You will have to generate a new SSH key.
 
-after generation, we will have two files at the location specified by the tool (or the custom location we chose). Generally, that's the folder `.ssh` in our home directory. If we navigate to that directory (`cd $HOME/.ssh`) and look at the files (`ls`), we'll see files named `id_rsa` and `id_rsa.pub`. The one that ends with `.pub` is the *public* key.
+after generation, we will have two files at the location specified by the tool (or the custom location we chose). Generally, that's the folder `.ssh` in our home directory. If we navigate to that directory (`cd $HOME/.ssh`) and look at the files (`ls`), we'll see files named `id_rsa` and `id_rsa.pub` (or maybe `id_ed25519` and `id_ed25519.pub` or something else). The one that ends with `.pub` is the *public* key.
 
 #### an alias...
 
@@ -492,7 +492,7 @@ in order for all this to be useful, we need to tell Codeberg about our SSH key.
 
 ### `git push`, take two
 
-we can now call `git push` again and again now without having to repeat our credentials every time. We can also call `git pull` for our private repositories.
+whether we're using HTTPS or SSH, we can now call `git push` again and again now without having to repeat our credentials every time. We can also call `git pull` for our private repositories.
 
 ## summary