Merge pull request #485 from crd/argument_types

Use correct brackets to indicate mandatory/optional parameters

Author: ben

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

@@ -64,7 +64,7 @@ Notice that these remotes use a variety of protocols; we'll cover more about thi
 ==== Adding Remote Repositories
 
 We've mentioned and given some demonstrations of adding remote repositories in previous sections, but here is how to do it explicitly.(((git commands, remote)))
-To add a new remote Git repository as a shortname you can reference easily, run `git remote add [shortname] [url]`:
+To add a new remote Git repository as a shortname you can reference easily, run `git remote add <shortname> <url>`:
 
 [source,console]
 ----

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

@@ -121,7 +121,7 @@ You can see that the changes have been reverted.
 
 [IMPORTANT]
 =====
-It's important to understand that `git checkout -- [file]` is a dangerous command.
+It's important to understand that `git checkout -- <file>` is a dangerous command.
 Any changes you made to that file are gone – you just copied another file over it.
 Don't ever use this command unless you absolutely know that you don't want the file.
 =====

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

@@ -3,7 +3,7 @@
 
 (((branches, remote)))(((references, remote)))
 Remote references are references (pointers) in your remote repositories, including branches, tags, and so on.
-You can get a full list of remote references explicitly with `git ls-remote (remote)`, or `git remote show (remote)` for remote branches as well as more information.
+You can get a full list of remote references explicitly with `git ls-remote [remote]`, or `git remote show [remote]` for remote branches as well as more information.
 Nevertheless, a more common way is to take advantage of remote-tracking branches.
 
 Remote-tracking branches are references to the state of remote branches.
@@ -65,7 +65,7 @@ Your local branches aren't automatically synchronized to the remotes you write t
 That way, you can use private branches for work you don't want to share, and push up only the topic branches you want to collaborate on.
 
 If you have a branch named `serverfix` that you want to work on with others, you can push it up the same way you pushed your first branch.
-Run `git push (remote) (branch)`:(((git commands, push)))
+Run `git push <remote> <branch>`:(((git commands, push)))
 
 [source,console]
 ----