From 2de9b71138171dca7279db3b3fe67e868c76d921 Mon Sep 17 00:00:00 2001
From: Thomas Ackermann
Date: Mon, 21 Jan 2013 20:17:53 +0100
Subject: Documentation: the name of the system is 'Git', not 'git'
Signed-off-by: Thomas Ackermann
Signed-off-by: Junio C Hamano
---
Documentation/howto/revert-a-faulty-merge.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
(limited to 'Documentation/howto/revert-a-faulty-merge.txt')
diff --git a/Documentation/howto/revert-a-faulty-merge.txt b/Documentation/howto/revert-a-faulty-merge.txt
index 8a685483f4..075418eeeb 100644
--- a/Documentation/howto/revert-a-faulty-merge.txt
+++ b/Documentation/howto/revert-a-faulty-merge.txt
@@ -164,7 +164,7 @@ merged. So it's debugging hell, because now you don't have lots of small
changes that you can try to pinpoint which _part_ of it changes.
But does it all work? Sure it does. You can revert a merge, and from a
-purely technical angle, git did it very naturally and had no real
+purely technical angle, Git did it very naturally and had no real
troubles. It just considered it a change from "state before merge" to
"state after merge", and that was it. Nothing complicated, nothing odd,
nothing really dangerous. Git will do it without even thinking about it.
--
cgit v1.2.3