Merge pull request #1065 from grgbnc/fixes

Fix #1057 and #1058

Author: ben

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

@@ -39,7 +39,7 @@ image::images/remote-branches-2.png[Local and remote work can diverge.]
 To synchronize your work, you run a `git fetch origin` command.
 This command looks up which server ``origin'' is (in this case, it's `git.ourcompany.com`), fetches any data from it that you don't yet have, and updates your local database, moving your `origin/master` pointer to its new, more up-to-date position.
 
-.`git fetch` updates your remote references
+.`git fetch` updates your remote-tracking branches
 image::images/remote-branches-3.png[`git fetch` updates your remote references.]
 
 To demonstrate having multiple remote servers and what remote branches for those remote projects look like, let's assume you have another internal Git server that is used only for development by one of your sprint teams.
@@ -53,7 +53,7 @@ image::images/remote-branches-4.png[Adding another server as a remote.]
 Now, you can run `git fetch teamone` to fetch everything the remote `teamone` server has that you don't have yet.
 Because that server has a subset of the data your `origin` server has right now, Git fetches no data but sets a remote-tracking branch called `teamone/master` to point to the commit that `teamone` has as its `master` branch.
 
-.Remote tracking branch for `teamone/master`
+.Remote-tracking branch for `teamone/master`
 image::images/remote-branches-5.png[Remote tracking branch for `teamone/master`.]
 
 [[_pushing_branches]]