Update 2023-11-20-week8.md

_posts/weeks/2023-11-20-week8.md

@@ -157,7 +157,7 @@ As a group, discuss and **write in notes**:
 **Do this part as a group**, while logged into someone's account on `ieng6`. Here we will look at a branch in our code that is currently in developement and a work in progress. You and your group have been tasked with testing and debugging the new beta branch. This new branch includes adding even more functionality to the `ChatServer` you just pulled, such as semantic analysis based on emoji's used.
 
 1. Make sure you are in the `ChatServer` folder and run `git branch` to see the current branch we are in and `git branch -a` to list all available branches. Take a screenshot of these commands and add them to your shared lab doc.
-2. Notice the presence of the `week8-sprint` branch which is only available remotely. We will want to checkout the new `week8-sprint` branch by running `git checkout week8-sprint`. To ensure that we have the latest updates, let's run a fresh pull in order to update our files. Let's do that by running `git pull` and verify our branch by running another `git branch`. Go ahead and take a screenshot of these steps and add them to your document. Discuss with your group members and write a short summary of what you just did in steps 1-2.
+2. Notice the presence of the `week8-sprint` branch which is only available remotely. We will want to checkout the new `week8-sprint` branch by running `git checkout week8-sprint`. Normally performing a `git checkout` will update your current repo to that branch, but to ensure that we have the latest updates, you can always run a fresh pull in order to update our files. Let's do that by running `git pull` and verify our branch by running another `git branch`. Go ahead and take a screenshot of these steps and add them to your document. Discuss with your group members and write a short summary of what you just did in steps 1-2.
 
 Fun Fact: [Sprint](https://www.codecademy.com/resources/blog/what-is-a-sprint/) is a common Software Engineering technique used to complete project milestones.
 
@@ -179,7 +179,12 @@ do this. Again, use `jdb` commands to find:
     - The local variables in `index` and `analysis` when the exception is happening
 
 Then, diagnose and fix the bug so that all the tests pass. Make a commit with
-the fix and push it to Github. Paste the Github link to the commit in your notes.
+the fix and push it to Github. Paste the Github link to the commit in your notes. Recall from lecture the following terminal commands for adding files, commiting changes and pushing said changes:
+```
+git add
+git commit
+git push
+```
 
 **Write down in notes:**