From 38faa4263150f619d777a29d497a52588e9f76a7 Mon Sep 17 00:00:00 2001
From: Mattias Andrée <maandree@operamail.com>
Date: Wed, 8 Apr 2015 23:34:11 +0200
Subject: ...
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Mattias Andrée <maandree@operamail.com>
---
using-git.texinfo | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/using-git.texinfo b/using-git.texinfo
index 8479369..f3c73e3 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -2052,10 +2052,10 @@ Assume your project is in Swedish, everyone
that understands Swedish will be able to
translate it to any other language. So far
it would be okay to write anything in Swedish,
-but once it has been translate, for example
+but once it has been translated, for example
to English, additional translators that do
not understand Swedish can contribute with
-additional translators. Now it is perferable
+additional translations. Now it is perferable
with English, while the translators can
understand everything that are should translate
they do not understand anything else.
@@ -2163,7 +2163,7 @@ with all such information in the top of
your repository.
@item @file{HACKING} @i{(optional)}
-For complex project you can have a file
+For complex projects you can have a file
named @file{HACKING} with information
about how to modify the code.
--
cgit v1.2.3-70-g09d2