Merge branch 'maint'

* maint:
git-show-ref.txt: remove word and make consistent
git-svn documentation: fix typo in 'rebase vs. pull/merge' section

diff --combined Documentation/git-svn.txt
index ca3fc3de1fcfc3509a9d5d1ff268c9673bafc3c0,74be8435cccf402dce2c95338b9553101b431b88..bb22d8e71281af3b00f5538e552a448d878667b4
--- 1/Documentation/git-svn.txt
--- 2/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@@ -398,14 -398,6 +398,14 @@@ after the authors-file is modified shou
  
  config key: svn.authorsfile
  
 +--authors-prog=<filename>::
 +
 +If this option is specified, for each SVN committer name that does not
 +exist in the authors file, the given file is executed with the committer
 +name as the first argument.  The program is expected to return a single
 +line of the form "Name <email>", which will be treated as if included in
 +the authors file.
 +
  -q::
  --quiet::
        Make 'git-svn' less verbose. Specify a second time to make it
@@@ -623,7 -615,7 +623,7 @@@ pulled or merged from.  This is becaus
  If you use `git svn set-tree A..B` to commit several diffs and you do
  not have the latest remotes/git-svn merged into my-branch, you should
  use `git svn rebase` to update your work branch instead of `git pull` or
- `git merge`.  `pull`/`merge' can cause non-linear history to be flattened
+ `git merge`.  `pull`/`merge` can cause non-linear history to be flattened
  when committing into SVN, which can lead to merge commits reversing
  previous commits in SVN.