From 88324fb400abe78bcf614cbd8cb03c5c31ae41ac Mon Sep 17 00:00:00 2001
From: AAshGray <193518051+AAshGray@users.noreply.github.com>
Date: Tue, 7 Jan 2025 11:33:05 -0800
Subject: [PATCH] Added a section

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index ecb5364..6246439 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,8 @@
 # github-intro
 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!
 
+## This lession is on how to use git and GitHub
+And this section is a change I made to the original document as part of the instructions.
 
 ## Fork the Repository (repo)
 
@@ -100,4 +102,4 @@ Introduction to using git and GitHub. Will lead you through your first fork, clo
 1. This will take you to a new page. At the bottom of the page you should see a visual representation of the differences (diff) your new change will introduce. Add a title and description to your pull request (PR).
 1. Click *Create pull request* to open the pull request.
 1. Congrats! You have created your first pull request!
-1. In Canvas, please copy the link to the pull request you created to submit your assignment. For this practice exercise I will not be merging your request. But in a real open-source repository, a *maintainer* would give you feedback on your changes, and if they were happy with them the would *merge* your PR (accept your changes into the original version).
+1. In Canvas, please copy the link to the pull request you created to submit your assignment. For this practice exercise I will not be merging your request. But in a real open-source repository, a *maintainer* would give you feedback on your changes, and if they were happy with them the would *merge* your PR (accept your changes into the original version).
\ No newline at end of file