summaryrefslogtreecommitdiff
path: root/Documentation/git-diff-index.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-12-29 09:20:06 (GMT)
committerJunio C Hamano <junkio@cox.net>2005-12-29 09:32:56 (GMT)
commit89438677abaae1a8ffc3c0905f3355a590da7bf4 (patch)
treef1d43ab8459bcc2010220c32c03001e7588b26f6 /Documentation/git-diff-index.txt
parentf1ec72ba1e52783179a7da7defaab0458c895617 (diff)
downloadgit-89438677abaae1a8ffc3c0905f3355a590da7bf4.zip
git-89438677abaae1a8ffc3c0905f3355a590da7bf4.tar.gz
git-89438677abaae1a8ffc3c0905f3355a590da7bf4.tar.bz2
Documentation: spell.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-diff-index.txt')
-rw-r--r--Documentation/git-diff-index.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-diff-index.txt b/Documentation/git-diff-index.txt
index dba6d30..5d2096a 100644
--- a/Documentation/git-diff-index.txt
+++ b/Documentation/git-diff-index.txt
@@ -53,7 +53,7 @@ If '--cached' is specified, it allows you to ask:
contents (the ones I'd write with a "git-write-tree")
For example, let's say that you have worked on your working directory, updated
-some files in the index and are ready to commit. You want to see eactly
+some files in the index and are ready to commit. You want to see exactly
*what* you are going to commit is without having to write a new tree
object and compare it that way, and to do that, you just do
@@ -110,7 +110,7 @@ NOTE: As with other commands of this type, "git-diff-index" does not
actually look at the contents of the file at all. So maybe
`kernel/sched.c` hasn't actually changed, and it's just that you
touched it. In either case, it's a note that you need to
-"git-upate-index" it to make the index be in sync.
+"git-update-index" it to make the index be in sync.
NOTE: You can have a mixture of files show up as "has been updated"
and "is still dirty in the working directory" together. You can always