Merge pull request #645 from ben4ever/fix_capitalizations

Fix capitalizations for the word "Git"

Author: ben

book/03-git-branching/sections/remote-branches.asc

@@ -137,7 +137,7 @@ If you're on a tracking branch and type `git pull`, Git automatically knows whic
 When you clone a repository, it generally automatically creates a `master` branch that tracks `origin/master`.
 However, you can set up other tracking branches if you wish – ones that track branches on other remotes, or don't track the `master` branch.
 The simple case is the example you just saw, running `git checkout -b [branch] [remotename]/[branch]`.
-This is a common enough operation that git provides the `--track` shorthand:
+This is a common enough operation that Git provides the `--track` shorthand:
 
 [source,console]
 ----

book/04-git-server/sections/gitlab.asc

@@ -8,7 +8,7 @@ This is a bit more complex than the GitWeb option and likely requires more maint
 
 ==== Installation
 
-GitLab is a database-backed web application, so its installation is a bit more involved than some other git servers.
+GitLab is a database-backed web application, so its installation is a bit more involved than some other Git servers.
 Fortunately, this process is very well-documented and supported.
 
 There are a few methods you can pursue to install GitLab.
@@ -68,7 +68,7 @@ The types of permissions are too numerous to list here, but GitLab has a helpful
 
 ===== Projects
 
-A GitLab project roughly corresponds to a single git repository.
+A GitLab project roughly corresponds to a single Git repository.
 Every project belongs to a single namespace, either a user or a group.
 If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group's user-level permissions will also take effect.
 
@@ -81,7 +81,7 @@ Note that this controls both git ``fetch'' access as well as access to the web U
 
 GitLab includes support for hooks, both at a project or system level.
 For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur.
-This is a great way to connect your git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools.
+This is a great way to connect your Git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools.
 
 ==== Basic Usage
 
@@ -113,7 +113,7 @@ Each project's home page shows recent activity, and links along the top will lea
 
 ==== Working Together
 
-The simplest way of working together on a GitLab project is by giving another user direct push access to the git repository.
+The simplest way of working together on a GitLab project is by giving another user direct push access to the Git repository.
 You can add a user to a project by going to the ``Members'' section of that project's settings, and associating the new user with an access level (the different access levels are discussed a bit in <<_gitlab_groups_section>>).
 By giving a user an access level of ``Developer'' or above, that user can push commits and branches directly to the repository with impunity.
 

book/A-git-in-other-environments/sections/bash.asc

@@ -12,7 +12,7 @@ Copy it somewhere handy, like your home directory, and add this to your `.bashrc
 . ~/git-completion.bash
 -----
 
-Once that's done, change your directory to a git repository, and type:
+Once that's done, change your directory to a Git repository, and type:
 
 [source,console]
 ----