diff --git a/ssh_keygen_config.md b/ssh_keygen_config.md
index 35ca78c..34632b7 100644
--- a/ssh_keygen_config.md
+++ b/ssh_keygen_config.md
@@ -1,37 +1,87 @@
-# SSH keys and config file
+
+# General SSH Key Configuration
 
 Once you start computing you will be logging in to the CARC systems fairly often and having to type your username at the machine address will become tedious. In order to alleviate this tedium it is beneficial to generate ssh keys and a ssh config file. The ssh keys bypass the need to enter your password each time you log in, and the config file stores the addresses of all the machines you are logging in to. 
 
 ### SSH key generation
 First, set up your ssh key. To do this type in the terminal prompt:
 
-```bash
-ssh-keygen
-```
-Just keep hitting enter until the program finishes. We recommend that you decline setting up a passphrase as this defeats the convenience of having a SSH key. Now that your SSH key has been generated you need to copy it to your home directory at CARC. To do, open terminal and type:
 
-```bash
-ssh-copy-id yourusername@machinename.alliance.unm.edu
-```
+    ssh-keygen
+
+You will then be asked which file you would like to save your new key under. Press enter here so it will be saved at the default location.
+
+Next, it will ask you to enter a passphrase. If you don't want to create one, you can just hit enter at this prompt as well. If you would like to create one, you'll enter your password here, and then confirm it by entering that same password a second time. 
+
+After this point, your ssh key has been created. You should see the randomart image for your key:
+
+    The key's randomart image is:
+    +---[RSA 3072]----+
+    |            E.o+=|
+    |         o . = .*|
+    |        . = oo ==|
+    |         + oo @.=|
+    |        S +  B.=o|
+    |       o   o. .=.|
+    |      + o + . o+o|
+    |     o o o o .+ o|
+    |   .o       .  o |
+    +----[SHA256]-----+
+
+This is a mechanism built into ssh keys which take each character from the key itself and converts it into a unique image based off of the key you just created. It is meant to be a quick and easy way to compare ssh keys to make sure nothing has changed. 
+
+After this point, your ssh key will have been created in your `~/.ssh` directory. This directory should now have the following structure:
+
+    $ ls ~/.ssh
+    id_rsa  id_rsa.pub
+
+Now that your ssh key is created on your local machine, we need to copy over the public key to the server you want to connect to. 
+
+    ssh-copy-id <CARC-USERNAME>@hopper.alliance.unm.edu
+
+After you've entered your password, your public ssh key will be copied into your home directory on hopper. After this point, whenever you ssh from this machine it will check this key against the private key that was just generated in your .ssh directory, and let you in without prompting you for a password.
+
 Since your home directory is shared across all machines at CARC you only need to do this step once to enable ssh key access across all CARC machines. 
 
 ### SSH config file
 To make logging in to CARC even easier we also recommend setting up a ssh config file which allows you to simply type `ssh machinename` instead of your username at the machine address. To set up this file simply copy the example below and save it to a text document in your `ssh` folder, which is found at `~/.ssh/`. Change the user to your CARC username and you are set to log in quickly and efficiently. You can add machines based on which ones you have access to. 
 
-```bash
-Host wheeler
-    hostname wheeler.alliance.unm.edu
-    user CHANGEME
-    port 22
-Host hopper
-    hostname hopper.alliance.unm.edu
-    user CHANGEME
-    port 22
-Host xena
-    hostname xena.alliance.unm.edu
-    user CHANGEME
-    ForwardX11 yes
-    port 22
-```
 
+    Host wheeler
+        hostname wheeler.alliance.unm.edu
+        user CHANGEME
+        port 22
+    Host hopper
+        hostname hopper.alliance.unm.edu
+        user CHANGEME
+        port 22
+    Host xena
+        hostname xena.alliance.unm.edu
+        user CHANGEME
+        ForwardX11 yes
+        port 22
+
+
+# Troubleshooting & Git
+
+Note that on the CARC clusters by default, your ssh configuration file will contain the following:
+
+    # Added by Warewulf  xxxx-xx-xx
+    Host *
+    IdentityFile ~/.ssh/cluster
+    StrictHostKeyChecking=no
+
+This helps ensure you're able to connect freely across all of the CARC clusters, for example while logged in to hopper you can just type `ssh xena`.
+
+The issue here will arise if you need to add a new ssh key for some reason, say, you need to add an ssh key so you're able to make edits to a git repository from the CARC clusters. If this is the case, you can start by creating a new ssh key as explained in the previous steps of this tutorial. 
+
+You should then edit your `~/.ssh/config` file as mentioned above, and change the Host line under the warewulf defined section to the following:
+
+    # Added by Warewulf  xxxx-xx-xx
+    Host hopper*
+    IdentityFile ~/.ssh/cluster
+    StrictHostKeyChecking=no
+
+This will ensure git will use the default key on the system when cloning with ssh (which will be the new one you just created), and will properly verify your credentials after adding the new public key to your github account. If you do not do this step, you will recevie a permision error when trying to clone or push to a git repo using ssh.
 
+*This quickbyte was validated on 5/22/2024*
\ No newline at end of file