Merge pull request #18 from UMLCloudComputing/feat--Update-Tutorials-section

Feat  update tutorials section

Author: Gurpranked

docs/tutorials/Git Version Control/Basics/Branch.md

@@ -6,21 +6,21 @@ sidebar_position: 6
 
 ### Using Git branches
 
-A [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch) is a seperate version of the main repository.<br/>
+A [branch](./Index.md#branch) is a seperate version of the main repository.<br/>
 Branches are particuarly useful when a developer wants to update parts of a large project.
 
 Git branches allow development on a new features and designs independent from other work on the main branch.<br/>
-When the work is complete on a branch, it can be [merged](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#merge) back into the main branch/project.<br/>
+When the work is complete on a branch, it can be [merged](./Index.md#merge) back into the main branch/project.<br/>
 With branches, it's also possible to work on different parts of a project simultaneously without any part impacting another.
 
 ### Creating a new Branch
 
-Let's create a new [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch) to work on a feature without modifying the main project's working code:
+Let's create a new [branch](./Index.md#branch) to work on a feature without modifying the main project's working code:
 
 ``` bash
 [user@localhost] $ git branch hello-world-pictures
 ```
-The command `git branch hello-world-pictures` will create a new [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch) called "hello-world-pictures".<br />
+The command `git branch hello-world-pictures` will create a new [branch](./Index.md#branch) called "hello-world-pictures".<br />
 Let's confirm that the branch was created:
 ``` bash
 [user@localhost] $ git branch
@@ -29,12 +29,12 @@ hello-world-pictures
 ```
 > Important: Whenever creating new branches, the branch from which the *new* branch is sourced from is the branch which was mounted when the git branch command was called. In scenario above, the command was called from within the `master` branch. Hence, all the initial files and changes are sourced from the `master` branch for the `hello-world-pictures` branch.
 
-A new branch called "hello-world-pictures" has been created, however the `*` symbol indicates that we are currently still on the `master` [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch). 
+A new branch called "hello-world-pictures" has been created, however the `*` symbol indicates that we are currently still on the `master` [branch](./Index.md#branch). 
 > When viewing the output of `git branch`, the `*` symbol indicates the current branch.
 
 ![Git-Staging-Diagram-3](../../../../static/img/git-tutorial/git-workflow-3.png)
 
-In order to leave the `master` [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch) and change to the "hello-world-pictures" [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch) we have to use the [`checkout`](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#checkout) command. 
+In order to leave the `master` [branch](./Index.md) and change to the "hello-world-pictures" [branch](./Index.md) we have to use the [`checkout`](./Index.md#checkout) command. 
 
 ``` bash
 [user@localhost] $ git checkout hello-world-pictures
@@ -77,7 +77,7 @@ Then let's update our html code:
 </html>
 ```
 
-Let's [save and exit](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#basic-editing-on-vim) and check the status of the current [branch](./Index.md/#branch)
+Let's [save and exit](./New%20Files.md/#basic-editing-on-vim) and check the status of the current [branch](./Index.md#branch)
 
 ``` bash
 [user@localhost] $ git status
@@ -94,14 +94,14 @@ Untracked files:
 no changes added to commit (use "git add" and/or "git commit -a")
 ```
 
-The output indicates that there are tracked changes to `index.html`, however the file is not [staged](./Index.md/#stage) for a [commit](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#commit). Moreover, there is also the image `git.png` that is currently untracked.
+The output indicates that there are tracked changes to `index.html`, however the file is not [staged](./Index.md#stage) for a [commit](./Index.md#commit). Moreover, there is also the image `git.png` that is currently untracked.
 
-So let's add all the changes to the [staging area](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#staging-area):
+So let's add all the changes to the [staging area](./Index.md#staging-area):
 ``` bash
 [user@localhost] $ git add --all
 ```
 
-Now let's check the status of the [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch):
+Now let's check the status of the [branch](./Index.md#branch):
 ``` bash
 [user@localhost] $ git status
 On branch hello-world-pictures
@@ -113,7 +113,7 @@ Changes to be committed:
 
 Now all the changes are staged and can be committed.
 
-Since we're satifisied with our changes, let's [commit](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#commit) them to our [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch):
+Since we're satifisied with our changes, let's [commit](./Index.md#commit) them to our [branch](./Index.md#branch):
 ``` bash
 [user@localhost] $ git commit -m "feat: Added image to hello world"
 [hello-world-pictures 83d7fb0] feat: Added image to hello world
@@ -130,15 +130,15 @@ Let's check content within our branch:
 [user@localhost] $ ls
 git.png  index.html  README.md  styles.css
 ```
-Notice how the `hello-world-pictures` [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch) has the image `git.png`. As per the edits we've made, `index.html` should also have modified code to include the image. 
+Notice how the `hello-world-pictures` [branch](./Index.md#branch) has the image `git.png`. As per the edits we've made, `index.html` should also have modified code to include the image. 
 
 Now's let's change to the `master` branch using the `checkout` command:
 ``` bash
 [user@localhost] $ git checkout master
                    Switched to branch 'master'
 ```
 
-Finally let's check the content of this [branch](/docs/tutorials/Git%20Version%20Control/Basics/Index.md/#branch):
+Finally let's check the content of this [branch](./Index.md#branch):
 ``` bash
 [user@localhost] $ ls
 index.html  README.md  styles.css

docs/tutorials/Git Version Control/Basics/Commit.md

@@ -6,9 +6,9 @@ sidebar_position: 5
 
 ![Git-Staging-Diagram-2](../../../../static/img/git-tutorial/git-workflow-2.png)
 
-Commits keep track of progress and changes as we work. Git treats each [`commit`](./Index.md/#commit) as a "save point". It's a point in the project which can be reverted to if a bug is found, or you want to make a change. 
+Commits keep track of progress and changes as we work. Git treats each [`commit`](./Index.md#commit) as a "save point". It's a point in the project which can be reverted to if a bug is found, or you want to make a change. 
 
-Whenever performing a [`commit`](./Index.md/#commit), **always** include a commit **message**. 
+Whenever performing a [`commit`](./Index.md#commit), **always** include a commit **message**. 
 It's always best practice to do so and improves understanding of your code for others and subsequently maintainability of your project. 
 
 ``` bash
@@ -46,16 +46,16 @@ To show this let's update `index.html` slightly:
     </body>
 </html>
 ```
->Recall, to open a file to edit in your working directory with [Vim](./Index.md/#vim), enter the command `vim `*`filename`* and enter insert mode (`I` key on the keyboard). To save and exit enter normal mode (`esc` key) and enter the command `:wq` (write and quit).
+>Recall, to open a file to edit in your working directory with [Vim](./Index.md#vim), enter the command `vim `*`filename`* and enter insert mode (`I` key on the keyboard). To save and exit enter normal mode (`esc` key) and enter the command `:wq` (write and quit).
 
-Now let's check the status of our [repo](./Index.md/#repository-repo), however with the `--short` option to get a more compact response:
+Now let's check the status of our [repo](./Index.md#repository-repo), however with the `--short` option to get a more compact response:
 ``` bash 
 [user@localhost] $ git status --short
                    M index.html
 ```
 > Note: The `--short` option on `git status` is also synonymous with `-s`. Hence, either `git status -s` or `git status --short` can be used to perform the same action.
 
-Here's some valuable [information](./Index.md/#git-status-short) about short git status flags.
+Here's some valuable [information](./Index.md#git-status-short) about short git status flags.
 
 Now let's commit directly:
 ``` bash

docs/tutorials/Git Version Control/Basics/Getting Started.md

@@ -12,8 +12,8 @@ Creating a new folder for a project:
 [user@localhost] $ cd newProject
 ```
 
-[`mkdir`](./Index.md/#mkdir) makes a new directory. <br />
-[`cd`](./Index.md/#cd) changes the current working directory.
+[`mkdir`](./Index.md#mkdir) makes a new directory. <br />
+[`cd`](./Index.md#cd) changes the current working directory.
 
 ## Initialize Git
 Once in the correct folder, initialize git on the folder:

docs/tutorials/Git Version Control/Basics/Git Basics.md

@@ -10,12 +10,12 @@ Git is a version control system that helps collaborate on code and keep track of
 
 ## What does Git do?
 
-* Manage projects with [**repositories**](./Index.md/#repository).
+* Manage projects with [**repositories**](./Index.md#repository-repo).
 * **Clone** a project to work with a local copy.
-* Control changes with [**Staging**](./Index.md/#staging) and [**Committing**](./Index.md/#commit).
-* [**Branch**](./Index.md/#branch) and [**Merge**](./Index.md/#merge) to work on different parts and versions of a project.
-* [**Pull**](./Index.md/#pull) the latest version of the project a local copy.
-* [**Push**](./Index.md/#push) local updates to a project.
+* Control changes with [**Staging**](./Index.md#stage) and [**Committing**](./Index.md#commit).
+* [**Branch**](./Index.md#branch) and [**Merge**](./Index.md#merge) to work on different parts and versions of a project.
+* [**Pull**](./Index.md#pull) the latest version of the project a local copy.
+* [**Push**](./Index.md#push) local updates to a project.
 
 ## Git vs Github
 * Git and Github are <mark>not</mark> the same.
@@ -43,7 +43,7 @@ If installed properly, the output should be in format `git version X.Y`.
 ```
 
 ## Configuring Git
-When performing git [**commits**](./Index.md/#commit), git needs to know who you are. <br />
+When performing git [**commits**](./Index.md#commit), git needs to know who you are. <br />
 Configure the username and email for git with the following commands:
 ``` bash
 git config --global user.name "YOUR_USERNAME"

docs/tutorials/Git Version Control/Basics/Index.md

@@ -7,7 +7,10 @@ sidebar_position: 10
 Index of terminology within this tutorial
 
 ### Push 
->*noun*: To publish your changes to a repository: `git push`
+>*noun, verb*: To publish your changes to a repository: `git push`
+
+### Pull
+>*noun, verb*: To fetch and integrate changes in a remote [repository](#repository-repo) with the changes in a local [repository](#repository-repo). `git pull`*` remote-name branch-name`*
 
 ### Repository (*repo*)
 >*noun*: A type of centrally located storage where you can keep all your project's files and resources.

docs/tutorials/Git Version Control/Basics/Merge Conflicts.md

@@ -43,12 +43,12 @@ Second, we need open `index.html` for editing and adding in our new [image](http
     </body>
 </html>
 ```
-After saving and exiting, we need to [stage](./Index.md/#stage) all the changes:
+After saving and exiting, we need to [stage](./Index.md#stage) all the changes:
 ``` bash
 [user@localhost] $ git add --all
 ```
 
-Now let's [commit](./Index.md/#commit) the changes to the `hello-world-pictures` branch:
+Now let's [commit](./Index.md#commit) the changes to the `hello-world-pictures` branch:
 ``` bash
 [user@localhost] $ git commit -m "feat: Added hello world image"
 [hello-world-pictures 9356dc6] feat: added hello world image
@@ -63,7 +63,7 @@ Now let's merge the changes from `hello-world-pictures`:
 CONFLICT (content): Merge conflict in index.html
 Automatic merge failed; fix conflicts and then commit the result.
 ```
-Yikes! We've encountered a [merge conflict](./Index.md/#merge-conflict)! 
+Yikes! We've encountered a [merge conflict](./Index.md#merge-conflict)! 
 
 ## What is a Merge Conflict?
 

docs/tutorials/Git Version Control/Basics/Merging.md

@@ -6,7 +6,7 @@ sidebar_position: 7
 
 ## Merging Branches
 
-Branch [merging](./Index.md/#merge) allows the changes from one branch to be added to another, essentially combining the changes. Merging typically goes hand in hand with branches since the changes specific to a branch are often combined back to the main project code. A common scenario in industry is to use [branches](./Index.md/#branch) to work of specific issues, features, or perform code maintainence. Once the edits are complete, the [branch's](./Index.md/#branch) edits are [merged](./Index.md/#merge) back into a `master` or main branch which contains the code used in production. 
+Branch [merging](./Index.md#merge) allows the changes from one branch to be added to another, essentially combining the changes. Merging typically goes hand in hand with branches since the changes specific to a branch are often combined back to the main project code. A common scenario in industry is to use [branches](./Index.md#branch) to work of specific issues, features, or perform code maintainence. Once the edits are complete, the [branch's](./Index.md#branch) edits are [merged](./Index.md#merge) back into a `master` or main branch which contains the code used in production. 
 
 Let's demonstrate how to merge branches alongside a bit of review!
 
@@ -58,8 +58,8 @@ Great! Now since our modifications are unstaged, let's go ahead and stage them a
 ```
 > Note: The command above used the `-a` option to stage and commit all changes in one-step.
 
-Finally, now let's [merge](./Index.md/#merge) our changes back into the `master` branch! <br/>
-First we need to [`checkout`](./Index.md/#checkout) to to the `master` branch. 
+Finally, now let's [merge](./Index.md#merge) our changes back into the `master` branch! <br/>
+First we need to [`checkout`](./Index.md#checkout) to to the `master` branch. 
 ``` bash
 [user@localhost] $ git checkout master
 Switched to branch 'master'
@@ -80,4 +80,4 @@ Since we're done working on the `copyright-fix` branch and it's no longer needed
 Deleted branch copyright-fix (was 5be7c4a).
 ```
 
-Amazing! We successfully managed to add a new piece to our project using [branches](./Index.md/#branch) and sucessfully [merged](./Index.md/#merge) the changes back to the `master` [branch](./Index.md/#branch).
+Amazing! We successfully managed to add a new piece to our project using [branches](./Index.md#branch) and sucessfully [merged](./Index.md#merge) the changes back to the `master` [branch](./Index.md#branch).

docs/tutorials/Git Version Control/Basics/New Files.md

@@ -6,9 +6,9 @@ sidebar_position: 3
 
 ### Adding new Files
 
-Let's find out how to add new files to a git [repository](./Index.md/#repository-repo)! <br />
-Within this tutorial, we'll be using the [Vim](./Index.md/#vim) CLI text-edtior to create a edit files. <br /> This can just as easily be done with your prefered text-editor. <br />
-IE with `code .` to open the current working directory within [Visual Studio Code](./Index.md/#visual-studio-code).
+Let's find out how to add new files to a git [repository](./Index.md#repository-repo)! <br />
+Within this tutorial, we'll be using the [Vim](./Index.md#vim) CLI text-edtior to create a edit files. <br /> This can just as easily be done with your prefered text-editor. <br />
+IE with `code .` to open the current working directory within [Visual Studio Code](./Index.md#visual-studio-code).
 
 ``` shell
 [user@localhost] $ vim index.html
@@ -46,16 +46,16 @@ Let's put some code within `index.html`:
 </html>
 ```
 #### Basic Editing on Vim
->In order to enter content into `index.html` using [Vim](./Index.md/#vim), enter insert mode by pressing the "I" key on your keyboard. Then either type or paste the code into the editor. <br />
-To save and exit out of [Vim](./Index.md/#vim) simply press the escape key and then type and enter `:wq` (write and quit). 
+>In order to enter content into `index.html` using [Vim](./Index.md#vim), enter insert mode by pressing the "I" key on your keyboard. Then either type or paste the code into the editor. <br />
+To save and exit out of [Vim](./Index.md#vim) simply press the escape key and then type and enter `:wq` (write and quit). 
 
-Now let's check the contant of our directory using [`ls`](./Index.md/#ls):
+Now let's check the contant of our directory using [`ls`](./Index.md#ls):
 ``` shell
 [user@localhost] $ ls
                   index.html
 ```
 
-Since the file is within our directory now, let's check if it's part of our [repo](./Index.md/#repository-repo) using `git status`:
+Since the file is within our directory now, let's check if it's part of our [repo](./Index.md#repository-repo) using `git status`:
 ``` shell
 [user@localhost] $ git status
                 On branch master
@@ -75,4 +75,4 @@ There are two potentional states for files in a repository folder:
 * Tracked: git knows about these and they are in your repository
 * Untracked: files that are in your working directory, however not added to your repository.
 
-Adding the first files to an empty repository are all untracked. In order for them to be tracked, they must be [staged](./Index.md/#stage) or must add them to a [staging area](./Index.md/#staging-area)
+Adding the first files to an empty repository are all untracked. In order for them to be tracked, they must be [staged](./Index.md#stage) or must add them to a [staging area](./Index.md#staging-area)

docs/tutorials/Git Version Control/Basics/Staging Area.md

@@ -8,14 +8,14 @@ sidebar_position: 4
 
 As you are working on a project, you add, edit, and remove files. When you reach a satisfactory point, you should add the files to a staging area.
 
-[Staged](Index.md/#stage) files are ready to be [committed](./Index.md/#commit) to your working repository. 
+[Staged](Index.md#stage) files are ready to be [committed](./Index.md#commit) to your working repository. 
 
 Back to our `newProject`, we can now make `index.html` as a tracked file by simple adding it to the staging area using `git add`:
 ``` shell
 [user@localhost] $ git add index.html
 ```
 
-Now `index.html` should be [staged](./Index.md/#stage):
+Now `index.html` should be [staged](./Index.md#stage):
 ``` shell
 [user@localhost] $ git status
                   On branch master
@@ -31,7 +31,7 @@ In other words, the file is now added to the staging area!
 
 ### Staging more than one file
 
-It's often that we end up modifying more than one file within a project before we decide to [stage](./Index.md/#stage) them. Let's see how to [stage](./Index.md/#stage) them all at once:
+It's often that we end up modifying more than one file within a project before we decide to [stage](./Index.md#stage) them. Let's see how to [stage](./Index.md#stage) them all at once:
 
 Let's start by adding a `README.md` file to our repository to describe it:
 ``` shell
@@ -42,7 +42,7 @@ and add the following content:
 # Hello world
 This repository exists as part of a git tutorial!
 ```
->Recall to use the `:wq` command in [Vim](./Index.md/#vim) to write and quit.
+>Recall to use the `:wq` command in [Vim](./Index.md#vim) to write and quit.
 
 Let's also add a CSS file called `styles.css`:
 ``` shell
@@ -60,7 +60,7 @@ body {
     animation-duration: 4s;
 }
 ```
->Again, recall to use the `:wq` command in [Vim](./Index.md/#vim) to write and quit.
+>Again, recall to use the `:wq` command in [Vim](./Index.md#vim) to write and quit.
 
 Finally let's update `index.html` to include our new stylesheet (`styles.css`):
 ``` shell
@@ -80,7 +80,7 @@ Finally let's update `index.html` to include our new stylesheet (`styles.css`):
     </body>
 </html>
 ```
-> Once again, recall to use the `:wq` command in [Vim](./Index.md/#vim) to write and quit.
+> Once again, recall to use the `:wq` command in [Vim](./Index.md#vim) to write and quit.
 
 Now let's add all these new files and changes to our staging area using the following command:
 ``` shell