Standardize on <remote>, not <remotename> or <remote-name> for examples

I'm a big believer in consistency.

Author: robertpjday

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

@@ -104,7 +104,7 @@ As you just saw, to get data from your remote projects, you can run:(((git comma
 
 [source,console]
 ----
-$ git fetch <remote-name>
+$ git fetch <remote>
 ----
 
 The command goes out to that remote project and pulls down all the data from that remote project that you don't have yet.
@@ -123,7 +123,7 @@ Running `git pull` generally fetches data from the server you originally cloned
 ==== Pushing to Your Remotes
 
 When you have your project at a point that you want to share, you have to push it upstream.
-The command for this is simple: `git push <remote-name> <branch-name>`.(((git commands, push)))
+The command for this is simple: `git push <remote> <branch-name>`.(((git commands, push)))
 If you want to push your master branch to your `origin` server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you've done back up to the server:
 
 [source,console]
@@ -139,7 +139,7 @@ See <<_git_branching>> for more detailed information on how to push to remote se
 [[_inspecting_remote]]
 ==== Inspecting a Remote
 
-If you want to see more information about a particular remote, you can use the `git remote show <remote-name>` command.(((git commands, remote)))
+If you want to see more information about a particular remote, you can use the `git remote show <remote>` command.(((git commands, remote)))
 If you run this command with a particular shortname, such as `origin`, you get something like this:
 
 [source,console]

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

@@ -136,7 +136,7 @@ If you're on a tracking branch and type `git pull`, Git automatically knows whic
 
 When you clone a repository, it generally automatically creates a `master` branch that tracks `origin/master`.
 However, you can set up other tracking branches if you wish – ones that track branches on other remotes, or don't track the `master` branch.
-The simple case is the example you just saw, running `git checkout -b <branch> <remotename>/<branch>`.
+The simple case is the example you just saw, running `git checkout -b <branch> <remote>/<branch>`.
 This is a common enough operation that Git provides the `--track` shorthand:
 
 [source,console]