docs: Add references and update links

Author: Ady-Gould

02-getting-ready.md

@@ -1,18 +1,32 @@
-# Before you start (Required Software)
+# Required Software
 
-You will need to ensure one of the following combinations is installed:
+Before you start using Git you will need some software to be installed.
+
+For Windows users the combination is one of:
 - Microsoft Terminal and Git-SCM, or
 - Microsoft Terminal and Laragon
 
-## Microsoft Terminal Installation
+For MacOS users then either:
+- iTerm2 & Git, or
+- Warp & Git
+
+Mac users are able to install Git via the Git-SCM installer or via homebrew.
+
+For Linux users:
+- Git
+Linux users should find git installed, if not use the package manager appropriate for your version of Linux.
+
+## Windows Installations
+
+### Microsoft Terminal Installation
 
 This is a great way to interact with the command line.
 
 Open the Microsoft Store, and search for "Microsoft Terminal".
 
 Install the "Microsoft Terminal" version and not the preview.
 
-## Git Installation
+### Git Installation
 
 Easiest way is to download and use the Git SCM installer:
 
@@ -22,7 +36,7 @@ Use the 64 Bit version when possible.
 
 Run the installer and accept the defaults.
 
-## Laragon Installation
+### Laragon Installation
 
 Download the Full Installer from https://laragon.org/download/index.html.
 
@@ -133,3 +147,8 @@ Finally you are able to open the new terminal by clicking on the `v` and selecti
 You will now have your terminal open and ready:
 
 ![](./assets/pasted-image-20240216111239.png)
+
+
+# Advanced Users
+
+If you want to make your CLI look even cooler (more useful) then something like OhMyPosh (https://ohmyposh.dev/) may help.

04-git-started.md

@@ -4,7 +4,13 @@ We are now ready to get started, and create a repository and work with it.
 
 ## Initialising a Repository for a 'project'
 
-There are three main ways to start a project. Two of them presume you have no existing files to begin with, and the third when you have files in an existing folder.
+There are three main ways to start a project. 
+
+Two of them presume you have no existing files to begin with, and the third when you have files in an existing folder.
+
+- Create a folder (for the project) and initialise
+- Initialise with folder (project) name
+- Initialise with the existing folder and files
 
 ### Option 1: Create a folder then initialising
 
@@ -13,6 +19,7 @@ Use `mkdir` command to create the folder, change into the new folder, and then u
 Let's presume the new project will be in the `Duck-Rogers` folder.
 
 Use the `pwd` command to verify the folder:
+
 ![](pasted-image-20240216113101.png)
 
 You see that the Windows `\` have been reversed to `/` and the `:` removed.
@@ -31,7 +38,7 @@ The command prompt will now show either `(master)` or `(main)` - if it is `maste
 
 To create the `Duck-Rogers` folder and initialise in a single move, we do the following:
 
-```
+```shell
 git init Duck-Rogers
 cd Duck-Rogers
 ```

05-global-settings.md

@@ -24,7 +24,9 @@ git config --list --global
 
 ![](pasted-image-20240216124543.png)
 
-### Per Project Configuration
+## Per Project Configuration
+
+If you wish to change settings for a particular project, you can do so by using "Per Project" or "Local" configuration.
 
 These need to be repeated for any project that is not going to be listed under your 'global' config.
 

12-remotely-useful.md

@@ -6,3 +6,43 @@ A way that we can get around this is to use a Version Control Repository that is
 
 A Remote is a copy of Git running on a server somewhere else, usually with a GUI front end, most commonly a Web-based interface.
 
+There are many repository management systems run both for free and profit. It is also possible to create a self hosted web based repository management system.
+
+Common (and less common) systems include:
+- GitHub
+- GitLab
+- BitBucket
+- Gitea
+- GNU Savannah
+- GitBucket
+- Gogs
+
+# GitHub
+
+## Creating a GitHub account
+
+Go to https://github.com/join and on the sign-up page enter your details.
+
+When doing this, there are a couple of items to note:
+- The username needs to be unique.
+- You cannot reuse an email address.
+- You may use a personal email address or your TAFE student email.
+- Do NOT make the username offensive, as many prospective employers will look at your accounts!
+
+![[pasted-image-20240301120950.png]]
+
+The next step requires you to verify that you are not a bot by solving a puzzle.
+
+Once the puzzle is solved, you will then need to verify your email address.
+
+To do this GitHub will send you and email that contains a link. Opening this link will verify your email address.
+
+![[pasted-image-20240301121055.png]]
+
+Once you have verified your email address, you are all done and are now able to create your very first project on GitHub.
+
+![[pasted-image-20240301121111.png]]
+
+
+
+

99-references-and-resources.md

@@ -0,0 +1,11 @@
+# References  and Resources
+
+We would like to acknowledge the wide variety of resources on this subject and many others that are freely available for learners, researchers and developers.
+
+Some of these resources have inspired content, others are there as they are an alternative way to look at how to use and learn version control.
+
+## Bibliography
+
+QuickRef.ME. (n.d.). _Git Command Cheat Sheet & Quick Reference_. [online] Available at: https://quickref.me/git [Accessed 1 Mar. 2024].
+
+Stepp, M., Miller, J., Anderson, R., Wortzman, B., Fung, Z. and Matuszek, D. (n.d.). _Version Control and Git_. [online] Available at: https://homepage.divms.uiowa.edu/~sgoddard/Courses/CS2820/Lectures/1-VersionControl-and-Git.pdf [Accessed 1 Mar. 2024].

ReadMe.md

@@ -1,10 +1,17 @@
 # Introduction to Version Control
 
-This project contains notes and exercises on using GIT for version control.
+This project contains notes and exercises to assist newcomers to version control to learn "Git".
 
-It will also include links to other resources that may assist in learning the basics of version control using git.
+The project is split into multiple Markdown files that cover sections of using and working with Git.
 
-- [01 What is Version Control](01-What-is-version-control)
+![GitHub Downloads (all assets, all releases)](https://img.shields.io/github/downloads/AdyGCode/Intro-to-Version-Control/total)  ![GitHub commits since latest release](https://img.shields.io/github/commits-since/AdyGCode/Intro-to-Version-Control/latest)
+
+
+### Contents
+
+This ReadMe does not need a Table of contents, instead we provide links to each of the Markdown files that make up this tutorial and exercises.
+
+- [01 What is Version Control](01-what-is-version-control.md)
 - [02 Getting Ready](02-getting-ready.md)
 - [03 Repositories and Folders](03-repositories-and-folders.md)
 - [04 Git Started](04-git-started.md)
@@ -15,4 +22,6 @@ It will also include links to other resources that may assist in learning the ba
 - [09 Git History](09-git-history.md)
 - [10 Shaking the Tree](10-shaking-the-tree.md)
 - [11 Merging and Conflicts](11-merging-and-conflicts)
-- [12-Remotely useful](12-remotely-useful)
+- [12 Remotely useful](12-remotely-useful)
+- ...
+- [99 References and Resources](99-references-and-resources.md)