Made the changes requested after review

Author: MarkCBJSS

version-control/command-line/tutorial.md

@@ -40,7 +40,7 @@ To check the state of our working directory and the Staging area (where we hold
 $ git status
 ```
 
-> The above command will tell you which files in the current directory have been changed and stqged, which haven't and which files aren't being tracked by Git.
+> The above command will tell you which files in the current directory have been changed and staged, which haven't and which files aren't being tracked by Git.
 
 ### Add your file to the local repository and commit your changes
 When we create new files or change existing ones, we 'add' them to an index of items to be committed to the local repository. The 'commit' command saves our changes into the local repository.
@@ -51,10 +51,10 @@ $ git status
 $ git commit -m 'this is my first command-line commit!'
 ```
 
-> `.` will add **all** the files in the current directory and subdirectories. You should only use it when initialising your repository. The rest of the time you should specify the individual file names to be added.
+> `.` will add **all** the files in the current directory and subdirectories. You should only use it when initialising your repository. The rest of the time it's recommended that you specify the individual file names to be added.
 
 ### Check the Git commit history
-It's easy to check a list of commits in a repository by using the `log` command.
+To check a list of commits in a repository use the `log` command.
 
 ```bash
 $ git log
@@ -66,18 +66,19 @@ $ git log
 
 Before we can add files to a remote repository, we need to have created an account with a service that is hosting that repository. If you've not done that yet, head over to our tutorial: Get set-up with [Git and GitHub](../set-up/tutorial.html).
 
-If you've already done that, then great - simply run the commands below, adding in the correct remote repository URL, such as `https://github.com/codebar/tutorials.git`.
+If you've already done that, then great - just run the commands below, adding in the correct remote repository URL, such as `https://github.com/codebar/tutorials.git`.
 
 ```bash
 $ git remote add origin <repository-url>
 $ git push -u origin master
 ```
 
-> This is worth repeating: We first add the location of a remote repository, in our case the remote repo is on Github and we've callled it 'origin' as it's the original repository we cloned down to our system. Then we 'push' our changes to the origin's 'master' branch. When there, we can raise a new 'pull Request' (PR) to get the changes 'merged' into the live code. Check out 'Get set-up with [Git and GitHub]'(../set-up/tutorial.html) tutorial for full details around this.
+> This is worth repeating: We first add the location of a remote repository, in our case the remote repo is on Github and we've callled it 'origin' as it's the original repository we cloned down to our system. Then we 'push' our changes to the origin's 'master' branch. When there, we can raise a new 'Pull Request' (PR) to get the changes 'merged' into the live code. Check out 'Get set-up with [Git and GitHub]'(../set-up/tutorial.html) tutorial for full details around this.
 
 #### What is `remote`?
 
-`remote` is simply the URL of your repository in any online repository hosting service, such as GitHub. The command `git remote` lists all the remote repositories you have configured. You could have the same repository stored in many places like GitHub and GitLab or Heroku and in such cases you will add a remote repository reference to you local machine, as we did above, for each of the remote repositories you have.
+`remote` is the URL of your repository in any online repository hosting service, such as GitHub. The command `git remote` lists all the remote repositories you have configured. You could have the same repository stored in many places like GitHub and GitLab or Heroku and in such cases you will add a remote repository reference to you local machine, as we did above, for each of the remote repositories you have.
+`remote` is the URL of your repository in any online repository hosting service, such as GitHub. The command `git remote` lists all the remote repositories you have configured. You could have the same repository stored in many places like GitHub and GitLab or Heroku and in such cases you will add a remote repository reference to you local machine, as we did above, for each of the remote repositories you have.
 
 The structure of the command to add a new `remote` is `git remote <add|remove> <name of remote> <url of remote>`.
 
@@ -378,9 +379,9 @@ $ git push origin master
 
 
 ### Creating a Git Config file
+Git allows us to define configuration settings that affect either just the repository we're working with, such as the URL of the remote repository location, or global settings such as Aliases for common commands (see below). There's a great example over at [https://gist.github.com/pksunkara/988716](https://gist.github.com/pksunkara/988716)
 
-Create a file called `.gitconfig` in the root directory (parent folder) of your local Git repo by typing
-`git touch .gitconfig` in the terminal window. Now practise adding the following configuration items.
+Create a file called `.gitconfig` in the root directory (parent folder) of your local Git repo by typing `git touch .gitconfig` in the terminal window. Though it may look odd, this file doesn't have an extension such as `.txt` like typical files. Now let's practise modifying this file by adding the following configuration items.
 
 ### User name and email
 If you didn't add your name and email address in the Set-up tutorial, add them now. These are added to each Git commit so it's clear who made the commit to the repo.
@@ -390,7 +391,7 @@ $ git config --global user.name "Your Name"
 $ git config --global user.email "name@domain"
 ```
 
-If you want to just edit the `.gitconfig` file directly then add the following:
+If you want to just edit the `.gitconfig` file directly then look for it in your root folder, open in your favourite text editing software add the following:
 
 ```
 [user]
@@ -487,7 +488,7 @@ Try it out by running `git lg` in a terminal window. If the log is very long, yo
 ## Bonus
 ### Store commands in your history
 
-On the commandline you can use the up and down arrows to cycle back over the Git commands you've typed before. This can save time when retrying certain commands or allow you to fix them without retyping the whole command. We can add Add HISTSIZE and HISTFILESIZE to your `.bashrc` file to make sure plenty of commands are stored beyond the default 500. 
+On the command line you can use the up and down arrows to cycle back over the Git commands you've typed before. This can save time when retrying certain commands or allow you to fix them without retyping the whole command. We can Add HISTSIZE and HISTFILESIZE to your `.bashrc` file to make sure plenty of commands are stored beyond the default 500. 
 - **HISTSIZE** is the number of commands stored in memory when you are using the terminal.
 - **HISTFILESIZE** is the number of commands stored in memory for future sessions.
 
@@ -502,7 +503,7 @@ After typing a couple of commands in the terminal to generate some history, try
 
 ## The next step
 
-Get learning JavaScript, HTML, CSS, Ruby and more on [Codebar](http://tutorials.codebar.io/).
+Get learning JavaScript, HTML, CSS, Ruby and more on [codebar](http://tutorials.codebar.io/).
 
 -----
 This ends **Introduction to the Git command line** tutorial. Is there something you don't understand? Try and go through the provided resources with your coach. If you have any feedback, or can think of ways to improve this tutorial [send us an email](mailto:[email protected]) and let us know.

version-control/introduction/tutorial.md

@@ -70,7 +70,7 @@ There are a number of reasons we chose Git and Github, namely;
 - Github makes online collaboration easy. Open source code is a big part of today's life. By being able to retrieve and help existing projects, you can also contribute to them
 
 ### Projects on Github
-Once you've worked through the Git and Github tutorials here at Codebar, there are an incredible range of projects that you'll be able to access for free. These projects include operating systems, games, programming languages, books and more.
+Once you've worked through the Git and Github tutorials here at codebar, there are an incredible range of projects that you'll be able to access for free. These projects include operating systems, games, programming languages, books and more.
 
 - Go retro with a **Windows 95** simulation: [https://github.com/felixrieseberg/windows95](https://github.com/felixrieseberg/windows95)
 
@@ -89,7 +89,7 @@ To find more projects, just enter a search in Github and see what comes back!
 
 ## Key Terms and Definitions for Git
 
-As with any technology and related tool, there's a lot of terminology realted to Git and Github. Here's some of the most common terms and their definitions:
+As with any technology and related tool, there's a lot of terminology related to Git and Github. Here's some of the most common terms and their definitions:
 
 - **Repository**: A repository is where code is stored, it can be a local or remote repository. Also called a 'repo'
 
@@ -113,7 +113,7 @@ As with any technology and related tool, there's a lot of terminology realted to
 
 ### Aim for small and focused changes
 
-When using version control, you should commit every time you do a small piece of work, rather than working for hours in a row, changing too many things and then committing them is a great way to introduce issues that are hard to track down. What's more, it makes it harder to review changes you made and need merging into the current code base.
+When using version control, you should commit every time you do a small piece of work, rather than working for hours in a row. Changing too many things and then committing them is a common way to introduce issues that are hard to track down. What's more, it makes it harder to review changes you made and need merging into the current code base.
 
 For example, if you want to change the position of an element, the colour of all the links on your page and the font size dimensions of all paragraphs, you should do three commits, using messages that describe what you are doing each time.
 

version-control/set-up/tutorial.md

@@ -123,7 +123,7 @@ We need to copy to the clipboard the contents of the `id_rsa_pub` file we create
 ```bash
 pbcopy < ~/.ssh/id_rsa.pub
 ```
-Now return back to the broswer where your Github account is open. Give the SSH key a `Title` and paste the file contents into the `Key` field. When done, hit the `Add SSH Key` button. You may be prompted for your password, if so enter it and hit `Confirm Password` to complete this step.
+Now return back to the browser where your Github account is open. Give the SSH key a `Title` and paste the file contents into the `Key` field. When done, hit the `Add SSH Key` button. You may be prompted for your password, if so enter it and hit `Confirm Password` to complete this step.
 
 ![Adding Key text and title](images/setup-paste-key-text.png)