summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarkus Heidelberg <markus.heidelberg@web.de>2009-04-04 10:35:22 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-04-05 07:39:37 (GMT)
commit38b7ccbe8c6615c709a4a69071c46593a1494952 (patch)
treeb5137c1d31ba7f2441b406b0da5814b766f32102
parent3346330d708b9b786b16167cbbd4a3637b3a3517 (diff)
downloadgit-38b7ccbe8c6615c709a4a69071c46593a1494952.zip
git-38b7ccbe8c6615c709a4a69071c46593a1494952.tar.gz
git-38b7ccbe8c6615c709a4a69071c46593a1494952.tar.bz2
doc/git-pack-refs: fix two grammar issues
Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-pack-refs.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-pack-refs.txt b/Documentation/git-pack-refs.txt
index a5244d3..1ee99c2 100644
--- a/Documentation/git-pack-refs.txt
+++ b/Documentation/git-pack-refs.txt
@@ -26,7 +26,7 @@ problem by stashing the refs in a single file,
traditional `$GIT_DIR/refs` hierarchy, it is looked up in this
file and used if found.
-Subsequent updates to branches always creates new file under
+Subsequent updates to branches always create new files under
`$GIT_DIR/refs` hierarchy.
A recommended practice to deal with a repository with too many
@@ -35,7 +35,7 @@ occasionally run `git pack-refs \--prune`. Tags are by
definition stationary and are not expected to change. Branch
heads will be packed with the initial `pack-refs --all`, but
only the currently active branch heads will become unpacked,
-and next `pack-refs` (without `--all`) will leave them
+and the next `pack-refs` (without `--all`) will leave them
unpacked.