docs: Update link data

Author: Ady-Gould

03-repositories-and-folders.md

@@ -12,7 +12,7 @@ Open Terminal and then click the `v` next to the `+` on the tab bar.
 
 Select the *Command Prompt* option
 
-![[pasted-image-20240216105215.png)
+![](pasted-image-20240216105215.png)
 
 When the terminal opens use the following commands to change into your "user home" and make the `Source\Repos` folder.
 

04-git-started.md

@@ -13,7 +13,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)
+![](pasted-image-20240216113101.png)
 
 You see that the Windows `\` have been reversed to `/` and the `:` removed.
 
@@ -23,7 +23,7 @@ cd Duck-Rogers
 git init .
 ```
 
-![[pasted-image-20240216113320.png)
+![](pasted-image-20240216113320.png)
 
 The command prompt will now show either `(master)` or `(main)` - if it is `master`, we will show you later how to (a) change it to `main` for the current project and (b) to make `main` the default.
 
@@ -36,28 +36,28 @@ git init Duck-Rogers
 cd Duck-Rogers
 ```
 
-![[pasted-image-20240216113649.png)
+![](pasted-image-20240216113649.png)
 
-![[pasted-image-20240216113804.png)
+![](pasted-image-20240216113804.png)
 
 ### Option 3: Initialise project with existing files
 
 The best part of this is that you are basically able to use the previous options, except the folder already exists.
 
 For example, if `Duck-Rogers` already exist and has files, then, if we are at the parent folder for  Duck-Rogers we can use the `git init Duck-Rogers` command.
 
-![[pasted-image-20240216114404.png)
+![](pasted-image-20240216114404.png)
 
 If you are in the `Duck-Rogers` folder and there are files in the folder then using the `git init .` command will do the same thing.
 
-![[pasted-image-20240216114456.png)
+![](pasted-image-20240216114456.png)
 
 
 ## Verify Repository was Created
 
 To check it is created we use the `ls -la` command:
 
-![[pasted-image-20240216113831.png)
+![](pasted-image-20240216113831.png)
 
 Notice the last line. The `d` at the start tells you it is a folder (directory), and its name is `.git`. It is a hidden folder.
 

05-global-settings.md

@@ -15,14 +15,14 @@ git config --global user.email "YOUR EMAIL ADDRESS"
 
 The `--global` indicates that the changes are stored for this and all future projects.
 
-![[pasted-image-20240216124422.png)
+![](pasted-image-20240216124422.png)
 
 To see the global settings...
 ```shell
 git config --list --global
 ```
 
-![[pasted-image-20240216124543.png)
+![](pasted-image-20240216124543.png)
 
 ### Per Project Configuration
 
@@ -47,7 +47,7 @@ git config user.email "[email protected]"
 
 The `--global` indicates that the changes are stored for this and all future projects.
 
-![[pasted-image-20240216124422.png)
+![](pasted-image-20240216124422.png)
 
 
 ### Default "Branch" name to Main...
@@ -64,7 +64,7 @@ To change the current 'master branch' to be the 'main branch' we need to do the
 git branch -m master main
 ```
 
-![[pasted-image-20240216125018.png)
+![](pasted-image-20240216125018.png)
 
 
 
@@ -91,11 +91,11 @@ git config --global core.editor "notepad"
 
 Now when you enter `git commit` the Notepad editor will open. The command line will tell you it is waiting for the editor to close a file (`COMMIT_MESSAGE`).
 
-![[pasted-image-20240223102507.png)
+![](pasted-image-20240223102507.png)
 
 When Notepad is opened, it will show a set of comments that tell you details about the added files as comments.
 
-![[pasted-image-20240223102034.png)
+![](pasted-image-20240223102034.png)
 
 Now editing the commit message and adding the details that may be more than just a one liner is easy.
 

08-status-add-commit.md

@@ -5,7 +5,7 @@ Checking the status of the repository is done using the `git status` command:
 ```shell
 git status
 ```
-![[pasted-image-20240216121457.png)
+![](pasted-image-20240216121457.png)
 
 In this example, we have two files that are not "tracked" by the repository.
 
@@ -18,19 +18,19 @@ To add a file to be tracked we use `git add FILENAME`. For example:
 ```shell
 git add ReadMe.md
 ```
-![[pasted-image-20240216121921.png)
+![](pasted-image-20240216121921.png)
 
 Checking the status after adding shows:
 
-![[pasted-image-20240216122006.png)
+![](pasted-image-20240216122006.png)
 
 Once a file is tracked, any time you make changes and are happy with them, you should perform a `git status` and then `git add` the changed file.
 
-![[pasted-image-20240216122531.png)
+![](pasted-image-20240216122531.png)
 
 Here you see the file has been modified.
 
-![[pasted-image-20240216122620.png)
+![](pasted-image-20240216122620.png)
 
 After adding the changes, we see it is back to  'new'.
 
@@ -46,11 +46,11 @@ git commit -m "Commit message"
 
 In the above line the `-m` indicates that we are including a message.
 
-![[pasted-image-20240216122842.png)
+![](pasted-image-20240216122842.png)
 
 Now our `git status` should show:
 
-![[pasted-image-20240216123105.png)
+![](pasted-image-20240216123105.png)
 
 The committed file is still tracked, but as no changes have been made it does not show. 
 
@@ -74,15 +74,15 @@ Save the changes, then check the status of the repository.
 
 It should show the `ReadMe.md` has changed:
 
-![[pasted-image-20240216123506.png)
+![](pasted-image-20240216123506.png)
 
 **Add** the changes to the repo and **commit** them using the message:
 
 ```text
 feat(readme): Update ReadMe.md to include author and version
 ```
 
-![[pasted-image-20240216123759.png)
+![](pasted-image-20240216123759.png)
 
 
 
@@ -99,4 +99,4 @@ The easiest way out is to do the following:
 
 - **Option 2:** Press **`ESCAPE`**, then press and hold the **`SHIFT`** whilst typing **`Z`** twice - This is a save and quit
 
-![[pasted-image-20240216125345.png)
+![](pasted-image-20240216125345.png)

09-git-history.md

@@ -3,10 +3,10 @@
 ## History so Far...
 
 To see the history of the project so far we use...
-```bash
+```shell
 git log
 ```
-![[pasted-image-20240216123842.png)
+![](pasted-image-20240216123842.png)
 
 > **Note:** The history is shown in reverse order... newest first.
 
@@ -17,6 +17,6 @@ git log --oneline
 ```
 
 Which produces a shorthand version of the log:
-![[pasted-image-20240223100556.png)
+![](pasted-image-20240223100556.png)
 
 What is important is that the message shows in this log. It is a good idea *not* to have a very long first line to a commit message.

11-merging-and-conflicts.md

@@ -25,7 +25,7 @@ To resolve this we need to edit the file(s) with the errors and fix the changes
 
 The image below shows the conflict being reported.
 
-![[pasted-image-20240223114440.png)
+![](pasted-image-20240223114440.png)
 
 To resolve the conflicts you now edit the file (or files) with the conflicts.
 
@@ -59,8 +59,8 @@ git commit -m "MERGE SUMMARY MESSAGE"
 
 The image below shows a really bad commit message:
 
-![[pasted-image-20240223115404.png)
+![](pasted-image-20240223115404.png)
 
 If we now log the commits we will see a diagram of the branches with the conflict shown in red:
 
-![[pasted-image-20240223115456.png)
+![](pasted-image-20240223115456.png)