aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/i18n.txt
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2023-10-08 06:45:09 +0000
committerJunio C Hamano <gitster@pobox.com>2023-10-09 12:06:29 -0700
commitce14cc0b00098201f967346955804abd774174ea (patch)
tree87da2bbac39b08973b8a5e3944ddf7a21141a392 /Documentation/i18n.txt
parent859a6d6045e338a337cb7499100b1fa31c367fbf (diff)
downloadgit-ce14cc0b00098201f967346955804abd774174ea.tar.gz
documentation: fix subject/verb agreement
Diff best viewed with --color-diff. Signed-off-by: Elijah Newren <newren@gmail.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 0efb1153d2..3a866af4a4 100644
--- a/Documentation/i18n.txt
+++ b/Documentation/i18n.txt
@@ -34,7 +34,7 @@ project find it more convenient to use legacy encodings, Git
does not forbid it. However, there are a few things to keep in
mind.
-. 'git commit' and 'git commit-tree' issues
+. 'git commit' and 'git commit-tree' issue
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