From 71467a53e8defde7543082f2b43f33aa35e5975b Mon Sep 17 00:00:00 2001
From: Necobi <274595030+Necobi@users.noreply.github.com>
Date: Wed, 8 Apr 2026 11:50:31 -0700
Subject: [PATCH] Marked the 'fork respo' step as important

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 80fc888..e2e065e 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 Introduction to using git and GitHub. Will lead you through your first fork, clone, commit, and push. It is common to run into issues when going through this. Don't be shy in asking for help or coming to office hours!
 
 
-## Fork the Repository (repo)
+## Fork the Repository (repo)  THIS IS IMPORTANT TO REMEMBER
 
 1. Make sure you are logged into your GitHub account.
 1. Fork this repository (repo) by clicking the *fork* button.
@@ -10,8 +10,8 @@ Introduction to using git and GitHub. Will lead you through your first fork, clo
     > A fork is a *GitHub* concept, not a git concept. It's creating a copy of the repo in your online GitHub account, but it doesn't download the code to your computer. If you have used Replit before, this is similar to creating a fork there.
 1. Keep this browser window open,  we will return to it in a moment.
 
-
-## Navigate your command line
+    
+## Navigate your command line   
 1. Open your command line (Git Bash on Windows, Terminal on Mac).
 1. Create a new directory where you will store repositories for this course. By default this will be in your home directory, but you can choose to put it elsewhere if you like. Run the below command to make a directory named `sdev301`.
     ```