Tweak figure titles

Author: ben

en/book/05-distributed-git/chapter5.asc

@@ -193,8 +193,8 @@ John has a reference to the changes Jessica pushed up, but he has to merge them
 The merge goes smoothly — John’s commit history now looks like <<contrib_b>>.
 
 [[contrib_b]]
-.John’s repository after merging origin/master.
-image::images/18333fig0505-tn.png[John’s repository after merging origin/master.]
+.John’s repository after merging `origin/master`.
+image::images/18333fig0505-tn.png[John’s repository after merging `origin/master`.]
 
 Now, John can test his code to make sure it still works properly, and then he can push his new merged work up to the server:
 
@@ -208,8 +208,8 @@ Now, John can test his code to make sure it still works properly, and then he ca
 Finally, John’s commit history looks like <<contrib_c>>.
 
 [[contrib_c]]
-.John’s history after pushing to the origin server.
-image::images/18333fig0506-tn.png[John’s history after pushing to the origin server.]
+.John’s history after pushing to the `origin` server.
+image::images/18333fig0506-tn.png[John’s history after pushing to the `origin` server.]
 
 In the meantime, Jessica has been working on a topic branch. She’s created a topic branch called `issue54` and done three commits on that branch. She hasn’t fetched John’s changes yet, so her commit history looks like <<contrib_d>>.
 
@@ -515,8 +515,8 @@ On a project for which you’re not the maintainer, it’s generally easier to h
 Now, each of your topics is contained within a silo — similar to a patch queue — that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other as in <<psp_a>>.
 
 [[psp_a]]
-.Initial commit history with featureB work.
-image::images/18333fig0516-tn.png[Initial commit history with featureB work.]
+.Initial commit history with `featureB` work.
+image::images/18333fig0516-tn.png[Initial commit history with `featureB` work.]
 
 Let’s say the project maintainer has pulled in a bunch of other patches and tried your first branch, but it no longer cleanly merges. In this case, you can try to rebase that branch on top of `origin/master`, resolve the conflicts for the maintainer, and then resubmit your changes:
 
@@ -529,8 +529,8 @@ Let’s say the project maintainer has pulled in a bunch of other patches and tr
 This rewrites your history to now look like <<psp_b>>.
 
 [[psp_b]]
-.Commit history after featureA work.
-image::images/18333fig0517-tn.png[Commit history after featureA work.]
+.Commit history after `featureA` work.
+image::images/18333fig0517-tn.png[Commit history after `featureA` work.]
 
 Because you rebased the branch, you have to specify the `-f` to your push command in order to be able to replace the `featureA` branch on the server with a commit that isn’t a descendant of it. An alternative would be to push this new work to a different branch on the server (perhaps called `featureAv2`).
 
@@ -549,8 +549,8 @@ The `--squash` option takes all the work on the merged branch and squashes it in
 Now you can send the maintainer a message that you’ve made the requested changes and they can find those changes in your `featureBv2` branch (see <<psp_c>>).
 
 [[psp_c]]
-.Commit history after featureBv2 work.
-image::images/18333fig0518-tn.png[Commit history after featureBv2 work.]
+.Commit history after `featureBv2` work.
+image::images/18333fig0518-tn.png[Commit history after `featureBv2` work.]
 
 ==== Public Large Project
 
@@ -933,8 +933,8 @@ Other maintainers prefer to rebase or cherry-pick contributed work on top of the
 The other way to move introduced work from one branch to another is to cherry-pick it. A cherry-pick in Git is like a rebase for a single commit. It takes the patch that was introduced in a commit and tries to reapply it on the branch you’re currently on. This is useful if you have a number of commits on a topic branch and you want to integrate only one of them, or if you only have one commit on a topic branch and you’d prefer to cherry-pick it rather than run rebase. For example, suppose you have a project that looks like <<merwf_h>>.
 
 [[merwf_h]]
-.Example history before a cherry pick.
-image::images/18333fig0526-tn.png[Example history before a cherry pick.]
+.Example history before a cherry-pick.
+image::images/18333fig0526-tn.png[Example history before a cherry-pick.]
 
 If you want to pull commit `e43a6` into your master branch, you can run