summaryrefslogtreecommitdiff
path: root/Documentation/git-p4import.txt
diff options
context:
space:
mode:
authorFrancis Daly <francis@daoine.org>2006-06-07 12:56:45 (GMT)
committerJunio C Hamano <junkio@cox.net>2006-06-07 18:49:35 (GMT)
commit3742506578dda5de2fe97e403f04150a85ffef17 (patch)
tree9e7e042b220c4d0567d6a6d6a5014ca3bdab5356 /Documentation/git-p4import.txt
parent17cf250aff26d3baa6b311a3404f1a932e16cf17 (diff)
downloadgit-3742506578dda5de2fe97e403f04150a85ffef17.zip
git-3742506578dda5de2fe97e403f04150a85ffef17.tar.gz
git-3742506578dda5de2fe97e403f04150a85ffef17.tar.bz2
Some doc typo fixes
All should be clear enough, except perhaps committish / commitish. I just kept the more-used one within the current docs. [jc: with rephrasing of check-ref-format description later discussed on the list] Signed-off-by: Francis Daly <francis@daoine.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-p4import.txt')
-rw-r--r--Documentation/git-p4import.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-p4import.txt b/Documentation/git-p4import.txt
index b8ff1e9..c198ff2 100644
--- a/Documentation/git-p4import.txt
+++ b/Documentation/git-p4import.txt
@@ -128,7 +128,7 @@ Therefore after the import you can use git to access any commit by its
Perforce number, eg. git show p4/327.
The tag associated with the HEAD commit is also how `git-p4import`
-determines if their are new changes to incrementally import from the
+determines if there are new changes to incrementally import from the
Perforce repository.
If you import from a repository with many thousands of changes