progit · ben · Jun 13, 2014 · Jun 10, 2014 · Jun 12, 2014 · Jun 13, 2014
diff --git a/book/03-git-branching/1-git-branching.asc b/book/03-git-branching/1-git-branching.asc
@@ -584,6 +584,7 @@ Some larger projects also have a `proposed` or `pu` (proposed updates) branch th
 The idea is that your branches are at various levels of stability; when they reach a more stable level, they're merged into the branch above them.
 Again, having multiple long-running branches isn't necessary, but it's often helpful, especially when you're dealing with very large or complex projects.
 
+[[_topic_branches]]
 ==== Topic Branches
 
 Topic branches, however, are useful in projects of any size.

diff --git a/book/05-distributed-git/1-distributed-git.asc b/book/05-distributed-git/1-distributed-git.asc
@@ -36,6 +36,7 @@ Then Jessica tries to push her changes, but the server rejects them.
 She is told that she's trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges.
 This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with.
 
+[[_integration_manager]]
 ==== Integration-Manager Workflow
 
 Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s.
@@ -56,7 +57,7 @@ The process works as follow (see <<wfdiag_b>>):
 .Integration-manager workflow.
 image::images/18333fig0502-tn.png[Integration-manager workflow.]
 
-This is a very common workflow with sites like GitHub, where it’s easy to fork a project and push your changes into your fork for everyone to see.
+This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see.
 One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time.
 Contributors don’t have to wait for the project to incorporate their changes – each party can work at their own pace.
 

diff --git a/book/06-github/1-github.asc b/book/06-github/1-github.asc
diff --git a/book/06-github/images/blink-3-seconds.png b/book/06-github/images/blink-3-seconds.png
diff --git a/book/06-github/images/blink-comment.png b/book/06-github/images/blink-comment.png
diff --git a/book/06-github/images/blink-final.png b/book/06-github/images/blink-final.png
diff --git a/book/06-github/images/blink-pr.png b/book/06-github/images/blink-pr.png
diff --git a/book/06-github/images/blink-pull-request-open copy.png b/book/06-github/images/blink-pull-request-open copy.png
diff --git a/book/06-github/images/blink-pull-request-open.png b/book/06-github/images/blink-pull-request-open.png
diff --git a/book/06-github/images/blink-start.png b/book/06-github/images/blink-start.png
diff --git a/book/06-github/images/collaborators.png b/book/06-github/images/collaborators.png
diff --git a/book/06-github/images/new-repo.png b/book/06-github/images/new-repo.png
diff --git a/book/07-git-tools/1-git-tools.asc b/book/07-git-tools/1-git-tools.asc
@@ -1,3 +1,4 @@
+[[_git_tools]]
 == Git Tools
 
 By now, you’ve learned most of the day-to-day commands and workflows that you need to manage or maintain a Git repository for your source code control.