From 472cf9eb3e0832d31cfd82e540f9dc2160f671c9 Mon Sep 17 00:00:00 2001 From: Michael Cade Date: Sun, 26 Jun 2022 12:12:35 +0100 Subject: [PATCH] Spelling & Grammar Day 38 --- Days/day38.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Days/day38.md b/Days/day38.md index 3be9b3f..727b326 100644 --- a/Days/day38.md +++ b/Days/day38.md @@ -23,11 +23,11 @@ This is where the details of the git repository are stored as well as the inform ### Staging Files -We then start working on our empty folder and maybe we add some source code as a first days work. We create our readme.mdfile and we can see that file in the directory, next we check our `git status` and it knows about the new readme.mdfile but we have not committed the file yet. +We then start working on our empty folder and maybe we add some source code on the first days of work. We create our readme.mdfile and we can see that file in the directory, next we check our `git status` and it knows about the new readme.mdfile but we have not committed the file yet. ![](Images/Day38_Git3.png) -We can stage our readme.mdfile with the `git add README.md` command then we can see changes to be committed which we did not have before and a green new file. +We can stage our readme.mdfile with the `git add README.md` command then we can see changes to be committed that we did not have before and a green new file. ![](Images/Day38_Git4.png) @@ -51,7 +51,7 @@ When nano opens you can then add your short and long description and then save t ### Committing Best Practices -There is a balance here to when to commit, commit often. We do not want to be waiting to be finished the project before committing, each commit should be meaningful and they also should not be coupled with non-relevant tasks with each other. If you have a bug fix and a typo make sure they are two separate commits as a best practice. +There is a balance here between when to commit and commit often. We do not want to be waiting to be finished the project before committing, each commit should be meaningful and they also should not be coupled with non-relevant tasks with each other. If you have a bug fix and a typo make sure they are two separate commits as a best practice. Make the commit message mean something. @@ -123,4 +123,4 @@ In the post tomorrow we will continue to look through these short examples of th - [Complete Git and GitHub Tutorial](https://www.youtube.com/watch?v=apGV9Kg7ics) - [Git cheatsheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet) -See you on [Day 39](day39.md) +See you on [Day 39](day39.md) \ No newline at end of file