summaryrefslogtreecommitdiff
path: root/Documentation/git-fsck-objects.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/git-fsck-objects.txt')
-rw-r--r--Documentation/git-fsck-objects.txt2
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