path: root/Documentation/git-fsck-objects.txt
diff options
authorHorst H. von Brand <>2006-06-03 20:27:26 (GMT)
committerJunio C Hamano <>2006-06-04 06:54:55 (GMT)
commitabda1ef590d94a5e15e7ce3b685b5c092a790cfa (patch)
tree73162a92b2abd5d87b86566899e321dd8ccef59c /Documentation/git-fsck-objects.txt
parent895f10c3b596ef955c7f252717e5b4668530c569 (diff)
Documentation: Spelling fixes
Signed-off-by: Horst H. von Brand <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-fsck-objects.txt')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-fsck-objects.txt b/Documentation/git-fsck-objects.txt
index 93ce9dc..d0af99d 100644
--- a/Documentation/git-fsck-objects.txt
+++ b/Documentation/git-fsck-objects.txt
@@ -71,7 +71,7 @@ sorted properly etc), but on the whole if "git-fsck-objects" is happy, you
do have a valid tree.
Any corrupt objects you will have to find in backups or other archives
-(ie you can just remove them and do an "rsync" with some other site in
+(i.e., you can just remove them and do an "rsync" with some other site in
the hopes that somebody else has the object you have corrupted).
Of course, "valid tree" doesn't mean that it wasn't generated by some