Merge pull request #880 from rpjday/getting_git_on_a_server

Rename "Getting Git on a Server" link to reflect the section name

Author: ben

book/04-git-server/sections/git-on-a-server.asc

@@ -1,4 +1,4 @@
-[[_git_on_the_server]]
+[[_getting_git_on_a_server]]
 === Getting Git on a Server
 
 Now we'll cover setting up a Git service running these protocols on your own server.

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

@@ -46,7 +46,7 @@ Then, you can push to and pull from that remote via your new remote name `local_
 The pros of file-based repositories are that they're simple and they use existing file permissions and network access.
 If you already have a shared filesystem to which your whole team has access, setting up a repository is very easy.
 You stick the bare repository copy somewhere everyone has shared access to and set the read/write permissions as you would for any other shared directory.
-We'll discuss how to export a bare repository copy for this purpose in <<_git_on_the_server>>.
+We'll discuss how to export a bare repository copy for this purpose in <<_getting_git_on_a_server>>.
 
 This is also a nice option for quickly grabbing work from someone else's working repository.
 If you and a co-worker are working on the same project and they want you to check something out, running a command like `git pull /home/john/project` is often easier than them pushing to a remote server and you subsequently fetching from it.