Merge branch 'kb/diff-blob-blob-doc'

* kb/diff-blob-blob-doc:
Documentation: Move "git diff <blob> <blob>"

diff --combined Documentation/git-diff.txt
index a7b46208f62c81b63ef4b8fdc5cf3ac67bd8b541,5effe97991c731ead12b817f1bd6c8a979bc9591..78d6d50489502638013509fbf72c811b50bfee86
--- 1/Documentation/git-diff.txt
--- 2/Documentation/git-diff.txt
+++ b/Documentation/git-diff.txt
@@@ -18,14 -18,14 +18,14 @@@ SYNOPSI
  DESCRIPTION
  -----------
  Show changes between the working tree and the index or a tree, changes
- between the index and a tree, changes between two trees, or changes
- between two files on disk.
+ between the index and a tree, changes between two trees, changes between
+ two blob objects, or changes between two files on disk.
  
  'git diff' [--options] [--] [<path>...]::
  
        This form is to view the changes you made relative to
        the index (staging area for the next commit).  In other
 -      words, the differences are what you _could_ tell git to
 +      words, the differences are what you _could_ tell Git to
        further add to the index but you still haven't.  You can
        stage these changes by using linkgit:git-add[1].
  +
@@@ -56,11 -56,6 +56,6 @@@ directories. This behavior can be force
        This is to view the changes between two arbitrary
        <commit>.
  
- 'git diff' [options] <blob> <blob>::
- 
-       This form is to view the differences between the raw
-       contents of two blob objects.
- 
  'git diff' [--options] <commit>..<commit> [--] [<path>...]::
  
        This is synonymous to the previous form.  If <commit> on
@@@ -87,6 -82,11 +82,11 @@@ and the range notations ("<commit>..<co
  "<commit>\...<commit>") do not mean a range as defined in the
  "SPECIFYING RANGES" section in linkgit:gitrevisions[7].
  
+ 'git diff' [options] <blob> <blob>::
+ 
+       This form is to view the differences between the raw
+       contents of two blob objects.
+ 
  OPTIONS
  -------
  :git-diff: 1