Autogenerated man pages for v1.4.0-rc1-gfd7e

[git.git] / man1 / git-p4import.1

diff --git a/man1/git-p4import.1 b/man1/git-p4import.1
index 0992144..0f5256c 100755 (executable)
--- a/man1/git-p4import.1
+++ b/man1/git-p4import.1
@@ -129,7 +129,7 @@ Another option is to create multiple symlinks locally which all point to the sam
 A git tag of the form p4/xx is created for every change imported from the Perforce repository where xx is the Perforce changeset number\&. 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 Perforce repository\&.
+The tag associated with the HEAD commit is also how git\-p4import determines if there are new changes to incrementally import from the Perforce repository\&.
 
 
 If you import from a repository with many thousands of changes you will have an equal number of p4/xxxx git tags\&. Git tags can be expensive in terms of disk space and repository operations\&. If you don't need to perform further incremental imports, you may delete the tags\&.