Merge branch 'master' into update-gitlab-section

Author: HonkingGoose

book/01-introduction/sections/what-is-git.asc

@@ -1,4 +1,4 @@
-[[_what_is_git]]
+[[what_is_git_section]]
 === What is Git?
 
 So, what is Git in a nutshell?

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

@@ -282,7 +282,7 @@ Turn off this advice by setting config variable advice.detachedHead to false
 
 HEAD is now at 99ada87... Merge pull request #89 from schacon/appendix-final
 
-$ git checkout 2.0-beta-0.1
+$ git checkout v2.0-beta-0.1
 Previous HEAD position was 99ada87... Merge pull request #89 from schacon/appendix-final
 HEAD is now at df3f601... Add atlas.json and cover image
 ----

book/03-git-branching/sections/branch-management.asc

@@ -77,10 +77,10 @@ $ git branch --no-merged master
 ==== Changing a branch name
 
 [CAUTION]
-----
+====
 Do not rename branches that are still in use by other collaborators.
 Do not rename a branch like master/main/mainline without having read the section "Changing the master branch name".
-----
+====
 
 Suppose you have a branch that is called _bad-branch-name_ and you want to change it to _corrected-branch-name_, while keeping all history.
 You also want to change the branch name on the remote (GitHub, GitLab, other server).

book/03-git-branching/sections/nutshell.asc

@@ -3,13 +3,13 @@
 
 To really understand the way Git does branching, we need to take a step back and examine how Git stores its data.
 
-As you may remember from <<ch01-getting-started#_what_is_git>>, Git doesn't store data as a series of changesets or differences, but instead as a series of _snapshots_.
+As you may remember from <<ch01-getting-started#what_is_git_section>>, Git doesn't store data as a series of changesets or differences, but instead as a series of _snapshots_.
 
 When you make a commit, Git stores a commit object that contains a pointer to the snapshot of the content you staged.
 This object also contains the author's name and email address, the message that you typed, and pointers to the commit or commits that directly came before this commit (its parent or parents): zero parents for the initial commit, one parent for a normal commit, and multiple parents for a commit that results from a merge of two or more branches.
 
 To visualize this, let's assume that you have a directory containing three files, and you stage them all and commit.
-Staging the files computes a checksum for each one (the SHA-1 hash we mentioned in <<ch01-getting-started#_what_is_git>>), stores that version of the file in the Git repository (Git refers to them as _blobs_), and adds that checksum to the staging area:
+Staging the files computes a checksum for each one (the SHA-1 hash we mentioned in <<ch01-getting-started#what_is_git_section>>), stores that version of the file in the Git repository (Git refers to them as _blobs_), and adds that checksum to the staging area:
 
 [source,console]
 ----