Merge pull request #1860 from petk/patch-git

Capitalize Git

Author: ben

TRANSLATING.md

@@ -8,7 +8,7 @@ Pro Git is a book about a technical tool, therefore translating it is difficult
 
 The following are guidelines to help you on your way:
 * Before you begin, read the whole Git Pro book in English, so that you're aware of the content, and are familiar with the style used.
-* Ensure you have a good working knowledge of git, so that explaining the technical terms is doable.
+* Ensure you have a good working knowledge of Git, so that explaining the technical terms is doable.
 * Stick to a common style and format for the translation.
 * Be sure to read and understand the basics of [Asciidoc formatting](https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/). Not following the asciidoc syntax can lead to problems with building/compilation of the pdf, epub and html files needed for the book.
 

book/02-git-basics/sections/remotes.asc

@@ -129,10 +129,10 @@ Running `git pull` generally fetches data from the server you originally cloned
 
 [NOTE]
 ====
-From git version 2.27 onward, `git pull` will give a warning if the `pull.rebase` variable is not set.
+From Git version 2.27 onward, `git pull` will give a warning if the `pull.rebase` variable is not set.
 Git will keep warning you until you set the variable.
 
-If you want the default behavior of git (fast-forward if possible, else create a merge commit):
+If you want the default behavior of Git (fast-forward if possible, else create a merge commit):
 `git config --global pull.rebase "false"`
 
 If you want to rebase when pulling:

book/09-git-and-other-scms/sections/import-bzr.asc

@@ -98,7 +98,7 @@ $ git init git-repo
 $ cd git-repo
 ----
 
-Pull the `master` branch into git:
+Pull the `master` branch into Git:
 
 [source,console]
 ----

book/10-git-internals/sections/refs.asc

@@ -73,7 +73,7 @@ The answer is the HEAD file.
 Usually the HEAD file is a symbolic reference to the branch you're currently on.
 By symbolic reference, we mean that unlike a normal reference, it contains a pointer to another reference.
 
-However in some rare cases the HEAD file may contain the SHA-1 value of a git object.
+However in some rare cases the HEAD file may contain the SHA-1 value of a Git object.
 This happens when you checkout a tag, commit, or remote branch, which puts your repository in https://git-scm.com/docs/git-checkout#_detached_head["detached HEAD"^] state.
 
 If you look at the file, you'll normally see something like this:

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

@@ -6,5 +6,5 @@ It provides a dedicated view in the IDE to work with Git and GitHub Pull Request
 .Version Control ToolWindow in JetBrains IDEs
 image::images/jb.png[Version Control ToolWindow in JetBrains IDEs]
 
-The integration relies on the command-line git client, and requires one to be installed.
+The integration relies on the command-line Git client, and requires one to be installed.
 The official documentation is available at https://www.jetbrains.com/help/idea/using-git-integration.html[^].

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

@@ -57,7 +57,7 @@ This happens, because the modules that ship with Windows PowerShell are signed w
 
 ===== Update PowerShell Prompt
 
-To include git information in your prompt, the posh-git module needs to be imported.
+To include Git information in your prompt, the posh-git module needs to be imported.
 To have posh-git imported every time PowerShell starts, execute the `Add-PoshGitToProfile` command which will add the import statement into your `$profile` script.
 This script is executed everytime you open a new PowerShell console.
 Keep in mind, that there are multiple `$profile` scripts.

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

@@ -1,14 +1,14 @@
 === Git in Sublime Text
 
-From version 3.2 onwards, Sublime Text has git integration in the editor.
+From version 3.2 onwards, Sublime Text has Git integration in the editor.
 
 The features are:
 
 * The sidebar will show the git status of files and folders with a badge/icon.
 * Files and folders that are in your .gitignore file will be faded out in the sidebar.
-* In the status bar, you can see the current git branch and how many modifications you have made.
+* In the status bar, you can see the current Git branch and how many modifications you have made.
 * All changes to a file are now visible via markers in the gutter.
-* You can use part of the Sublime Merge git client functionality from within Sublime Text.
+* You can use part of the Sublime Merge Git client functionality from within Sublime Text.
   This requires that Sublime Merge is installed.
   See: https://www.sublimemerge.com/[^].
 

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

@@ -1,7 +1,7 @@
 === Git in Visual Studio Code
 
-Visual Studio Code has git support built in.
-You will need to have git version 2.0.0 (or newer) installed.
+Visual Studio Code has Git support built in.
+You will need to have Git version 2.0.0 (or newer) installed.
 
 The main features are:
 

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

@@ -47,7 +47,7 @@ Instead of `vcs_info`, you might prefer the prompt customization script that shi
 
 Zsh is powerful enough that there are entire frameworks dedicated to making it better.
 One of them is called "oh-my-zsh", and it can be found at https://github.com/ohmyzsh/ohmyzsh[^].
-oh-my-zsh's plugin system comes with powerful git tab-completion, and it has a variety of prompt "themes", many of which display version-control data.
+oh-my-zsh's plugin system comes with powerful Git tab-completion, and it has a variety of prompt "themes", many of which display version-control data.
 <<oh_my_zsh_git>> is just one example of what can be done with this system.
 
 [[oh_my_zsh_git]]

book/B-embedding-git/sections/dulwich.asc

@@ -3,10 +3,10 @@
 (((Dulwich)))(((Python)))
 There is also a pure-Python Git implementation - Dulwich.
 The project is hosted under https://www.dulwich.io/[^].
-It aims to provide an interface to git repositories (both local and remote) that doesn't call out to git directly but instead uses pure Python.
+It aims to provide an interface to Git repositories (both local and remote) that doesn't call out to Git directly but instead uses pure Python.
 It has an optional C extensions though, that significantly improve the performance.
 
-Dulwich follows git design and separate two basic levels of API: plumbing and porcelain.
+Dulwich follows Git design and separate two basic levels of API: plumbing and porcelain.
 
 Here is an example of using the lower level API to access the commit message of the last commit: