[PATCH] use it's and its correctly in documentation

At one place in Documentation/tutorial.txt and several in the base
README, its was wrongly used in place of it's or vice versa.  One
instance remains somewhere in Documentation/howto/, which I didn't
correct because it's in a quotation.

Signed-off-by: Greg Louis <glouis@dynamicro.ca>
Signed-off-by: Junio C Hamano <junkio@cox.net>

diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 66b6e300a217d008de44c5be7e3f7e0f01179933..a2a7b7cd41d6011ea5ea434df57821a855140a3e 100644 (file)
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -891,7 +891,7 @@ an empty directory:
        mkdir my-git.git
 
 Then, make that directory into a GIT repository by running
        mkdir my-git.git
 
 Then, make that directory into a GIT repository by running

-git-init-db, but this time, since it's name is not the usual
+git-init-db, but this time, since its name is not the usual

 ".git", we do things slightly differently:
 
        GIT_DIR=my-git.git git-init-db
 ".git", we do things slightly differently:
 
        GIT_DIR=my-git.git git-init-db

diff --git a/README b/README
index 80cc27913e449fbc25f2df1c515abc294ba9afde..0bc00a7c84c79932881fa561513c2288227fa5b8 100644 (file)
--- a/README
+++ b/README
@@ -98,12 +98,12 @@ contents").
 In particular, since the blob is entirely defined by its data, if two
 files in a directory tree (or in multiple different versions of the
 repository) have the same contents, they will share the same blob
 In particular, since the blob is entirely defined by its data, if two
 files in a directory tree (or in multiple different versions of the
 repository) have the same contents, they will share the same blob

-object. The object is totally independent of it's location in the
+object. The object is totally independent of its location in the

 directory tree, and renaming a file does not change the object that
 file is associated with in any way.
 
 A blob is typically created when link:git-update-cache.html[git-update-cache]
 directory tree, and renaming a file does not change the object that
 file is associated with in any way.
 
 A blob is typically created when link:git-update-cache.html[git-update-cache]

-is run, and it's data can be accessed by link:git-cat-file.html[git-cat-file].
+is run, and its data can be accessed by link:git-cat-file.html[git-cat-file].

 
 Tree Object
 ~~~~~~~~~~~
 
 Tree Object
 ~~~~~~~~~~~


@@ -142,7 +142,7 @@ noticing that the blob stayed the same.  However, renames with data
 changes need a smarter "diff" implementation.
 
 A tree is created with link:git-write-tree.html[git-write-tree] and
 changes need a smarter "diff" implementation.
 
 A tree is created with link:git-write-tree.html[git-write-tree] and

-it's data can be accessed by link:git-ls-tree.html[git-ls-tree]
+its data can be accessed by link:git-ls-tree.html[git-ls-tree]

 
 Commit Object
 ~~~~~~~~~~~~~
 
 Commit Object
 ~~~~~~~~~~~~~


@@ -167,7 +167,7 @@ of the parents), and describing that makes no sense in this idiotic
 file manager.
 
 A commit is created with link:git-commit-tree.html[git-commit-tree] and
 file manager.
 
 A commit is created with link:git-commit-tree.html[git-commit-tree] and

-it's data can be accessed by link:git-cat-file.html[git-cat-file]
+its data can be accessed by link:git-cat-file.html[git-cat-file]

 
 Trust
 ~~~~~
 
 Trust
 ~~~~~


@@ -213,7 +213,7 @@ integrity; the trust framework (and signature provision and
 verification) has to come from outside.
 
 A tag is created with link:git-mktag.html[git-mktag] and
 verification) has to come from outside.
 
 A tag is created with link:git-mktag.html[git-mktag] and

-it's data can be accessed by link:git-cat-file.html[git-cat-file]
+its data can be accessed by link:git-cat-file.html[git-cat-file]

 
 
 The "index" aka "Current Directory Cache"
 
 
 The "index" aka "Current Directory Cache"