Merge branch 'bk/maint-cvsexportcommit' into maint

[git.git] / Documentation / git-clone.txt

diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 227f092e268497aad9c16cff4d796dabf60401de..cca14d6b5df042fcf48889e5ff00285ffc4c3009 100644 (file)
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -68,7 +68,7 @@ OPTIONS
        automatically setup .git/objects/info/alternates to
        obtain objects from the reference repository.  Using
        an already existing repository as an alternate will
        automatically setup .git/objects/info/alternates to
        obtain objects from the reference repository.  Using
        an already existing repository as an alternate will

-       require less objects to be copied from the repository
+       require fewer objects to be copied from the repository

        being cloned, reducing network and local storage costs.
 
 --quiet::
        being cloned, reducing network and local storage costs.
 
 --quiet::


@@ -111,11 +111,11 @@ OPTIONS
 
 --depth <depth>::
        Create a 'shallow' clone with a history truncated to the
 
 --depth <depth>::
        Create a 'shallow' clone with a history truncated to the

-       specified number of revs.  A shallow repository has
+       specified number of revisions.  A shallow repository has a

        number of limitations (you cannot clone or fetch from
        it, nor push from nor into it), but is adequate if you
        number of limitations (you cannot clone or fetch from
        it, nor push from nor into it), but is adequate if you

-       want to only look at near the tip of a large project
-       with a long history, and would want to send in a fixes
+       are only interested in the recent history of a large project
+       with a long history, and would want to send in fixes

        as patches.
 
 <repository>::
        as patches.
 
 <repository>::