diff --git a/cs-fundamentals/git.md b/cs-fundamentals/git.md
index 7b0c510c9a1d6fb2e5736e9337e50c0e40e66f76..60cb9cbf47f2ddb70ccbc93e0da14accda3910c4 100644
--- a/cs-fundamentals/git.md
+++ b/cs-fundamentals/git.md
@@ -1,12 +1,17 @@
 # Sub-Unit: Git
 
-Most people writing with software now use git to manage source code.
+Git is a [distributed version control system](https://en.wikipedia.org/wiki/Distributed_version_control). It allows users to manage and track versions of files as they are changed and updated, an important tool for programming projects, particularly where multiple people are involved in creating code. There are many different kinds of version control system, but most now use git to manage source code. 
 
 ## Learning Goals
-
-Learn to use the git version control system's most common features by using git to manage the development of a program.
+* Learn to use the git version control system's most common features by using git to manage the development of a program.
+* Familiarize yourself with the Gitlab web interface and navigating projects, groups, and repositories.
+* Understand the purpose and benefits of using a version control system.
 
 ## Resources
+- [Github Flow](https://docs.github.com/en/get-started/using-github/github-flow)
+- [GitKraken Tutorials](https://www.gitkraken.com/learn/git/tutorials)
+- [GitSCM Book](https://git-scm.com/book/en/v2/)
+
 ### How it works
 
 Git is a distributed version control system (VCS). Every copy of the code repository contains all the code, including all branches. You and I might both have a copy of the code that we work on independently and then share in GitLab so others can have the features we've added. While we treat GitLab as the canonical host of our files, this is by our choice and design (i.e. it is not imposed by git itself). There is no dependency on e.g. your Internet connection if you have cloned a git repository to your local machine.
@@ -26,7 +31,7 @@ Some key terms you will hear and read many times in git:
 * **rm**: remove a file from code in the next commit
 * **commit**: a collection of changes to source code with an ID and (usually) a message; think of this like "saving" your code
 * **push**: update the remote version of the repository to include all your local commits; in our case this means "put all my new commits in GitLab"
-* branch: a named set of code changes; branches are separate from each other, and a common use for branches is to work on something in a space that does not affect the main/master/production branch
+* **branch**: a named set of code changes; branches are separate from each other, and a common use for branches is to work on something in a space that does not affect the main/master/production branch
 
 As a rule:
 * Commit often (small diffs are easier to understand and debug)