Merge branch 'nd/sparse-doc' into maint-1.7.6

* nd/sparse-doc:
  git-read-tree.txt: update sparse checkout examples

diff --cc Documentation/git-read-tree.txt
index 1bd0317a42e587a28ae39b26da38889275bfd058,e9f4355d7db175efa6107e1bbb9985d94e0d8f82..5375549820bd6b9fecf3540b1e60ae50e74da0e6
--- 1/Documentation/git-read-tree.txt
--- 2/Documentation/git-read-tree.txt
+++ b/Documentation/git-read-tree.txt
@@@ -379,29 -378,29 +379,29 @@@ have finished your work-in-progress), a
  Sparse checkout
  ---------------
  
 -"Sparse checkout" allows to sparsely populate working directory.
 -It uses skip-worktree bit (see linkgit:git-update-index[1]) to tell
 -Git whether a file on working directory is worth looking at.
 +"Sparse checkout" allows populating the working directory sparsely.
 +It uses the skip-worktree bit (see linkgit:git-update-index[1]) to tell
 +Git whether a file in the working directory is worth looking at.
  
 -"git read-tree" and other merge-based commands ("git merge", "git
 -checkout"...) can help maintaining skip-worktree bitmap and working
 +'git read-tree' and other merge-based commands ('git merge', 'git
 +checkout'...) can help maintaining the skip-worktree bitmap and working
  directory update. `$GIT_DIR/info/sparse-checkout` is used to
 -define the skip-worktree reference bitmap. When "git read-tree" needs
 -to update working directory, it will reset skip-worktree bit in index
 +define the skip-worktree reference bitmap. When 'git read-tree' needs
 +to update the working directory, it resets the skip-worktree bit in the index
  based on this file, which uses the same syntax as .gitignore files.
 -If an entry matches a pattern in this file, skip-worktree will be
 -set on that entry. Otherwise, skip-worktree will be unset.
 +If an entry matches a pattern in this file, skip-worktree will not be
 +set on that entry. Otherwise, skip-worktree will be set.
  
  Then it compares the new skip-worktree value with the previous one. If
 -skip-worktree turns from unset to set, it will add the corresponding
 -file back. If it turns from set to unset, that file will be removed.
 +skip-worktree turns from set to unset, it will add the corresponding
 +file back. If it turns from unset to set, that file will be removed.
  
  While `$GIT_DIR/info/sparse-checkout` is usually used to specify what
 -files are in. You can also specify what files are _not_ in, using
 -negate patterns. For example, to remove file "unwanted":
 +files are in, you can also specify what files are _not_ in, using
 +negate patterns. For example, to remove the file `unwanted`:
  
  ----------------
- *
+ /*
  !unwanted
  ----------------
  
@@@ -413,11 -412,11 +413,11 @@@ directory with the `$GIT_DIR/info/spars
  follows:
  
  ----------------
- *
+ /*
  ----------------
  
 -Then you can disable sparse checkout. Sparse checkout support in "git
 -read-tree" and similar commands is disabled by default. You need to
 +Then you can disable sparse checkout. Sparse checkout support in 'git
 +read-tree' and similar commands is disabled by default. You need to
  turn `core.sparseCheckout` on in order to have sparse checkout
  support.