From: Joel Rosdahl <joel@rosdahl.net>
Date: Sat, 16 Jul 2011 13:43:58 +0000 (+0200)
Subject: Minor tweaks to HACKING.txt
X-Git-Tag: v3.2~232
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2b43c8baebfe504f38381b28e45ef9c2f760313c;p=thirdparty%2Fccache.git

Minor tweaks to HACKING.txt
---

diff --git a/HACKING.txt b/HACKING.txt
index b34c29e6c..36de458d6 100644
--- a/HACKING.txt
+++ b/HACKING.txt
@@ -8,7 +8,7 @@ Code formatting
   <http://www.emacswiki.org/emacs/SmartTabs>.
 * Use 4 spaces for indenting other code (and spaces for aligning).
 * Put the opening curly brace on a new line when defining a function, otherwise
-  at the end of the same row.
+  at the end of the same line.
 * Put no space between function name and the following parenthesis.
 * Put one space between if/switch/for/while/do and opening curly brace.
 * If possible, keep lines at most 80 character wide for a 2 character tab
@@ -42,7 +42,7 @@ Commit messages
 * Write a short description on the first line. If wanted, leave the second line
   empty and write a longer description on line three and below.
 * Start the short description with a capital letter. Optional: prefix the short
-  description with a context follow by a colon.
+  description with a context followed by a colon.
 * The short description should be in "command form" (see examples below).
 * Don't put a final period after the short description.
 * Keep lines in the message at most 75 characters wide.