aboutsummaryrefslogtreecommitdiff
path: root/Documentation/i18n.txt
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2008-01-03 15:18:07 +0100
committerJunio C Hamano <gitster@pobox.com>2008-01-03 09:15:17 -0800
commit790296fd8863d649054096191d33bacbbf5c2115 (patch)
treecdcd2549cfa71e3463ab1757aa1db1ad3b7188dc /Documentation/i18n.txt
parent698a68be7b0df6dd8d0880e0e2167cad8688a6ad (diff)
downloadgit-790296fd8863d649054096191d33bacbbf5c2115.tar.gz
git-790296fd8863d649054096191d33bacbbf5c2115.tar.xz
Fix grammar nits in documentation and in code comments.
Signed-off-by: Jim Meyering <meyering@redhat.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/i18n.txt')
-rw-r--r--Documentation/i18n.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/i18n.txt b/Documentation/i18n.txt
index b95f99be6..1e188e6e7 100644
--- a/Documentation/i18n.txt
+++ b/Documentation/i18n.txt
@@ -22,7 +22,7 @@ does not forbid it. However, there are a few things to keep in
mind.
. `git-commit-tree` (hence, `git-commit` which uses it) issues
- an warning if the commit log message given to it does not look
+ a warning if the commit log message given to it does not look
like a valid UTF-8 string, unless you explicitly say your
project uses a legacy encoding. The way to say this is to
have i18n.commitencoding in `.git/config` file, like this: