Merge pull request progit#289 from robblanco/its-typos

A few it's -> its grammar fixes

Author: ben

book/06-github/sections/3-maintaining.asc

@@ -245,7 +245,7 @@ Web notifications only exist on GitHub and you can only check them on GitHub. If
 .Notification center.
 image::images/maint-08-notifications-page.png[Notification center]
 
-If you click on that, you will see a list of all the items you have been notified about, grouped by project. You can filter to the notifications of a specific project by clicking on it's name in the left hand sidebar. You can also acknowledge the notification by clicking the checkmark icon next to any notification, or acknowledge _all_ of the notifications in a project by clicking the checkmark at the top of the group. There is also a mute button next to each checkmark that you can click to not receive any further notifications on that item.
+If you click on that, you will see a list of all the items you have been notified about, grouped by project. You can filter to the notifications of a specific project by clicking on its name in the left hand sidebar. You can also acknowledge the notification by clicking the checkmark icon next to any notification, or acknowledge _all_ of the notifications in a project by clicking the checkmark at the top of the group. There is also a mute button next to each checkmark that you can click to not receive any further notifications on that item.
 
 All of these tools are very useful for handling large numbers of notifications. Many GitHub power users will simply turn off email notifications entirely and manage all of their notifications through this screen.
 
@@ -328,4 +328,4 @@ image::images/maint-11-transfer.png[Transfer]
 
 This is helpful if you are abandoning a project and someone wants to take it over, or if your project is getting bigger and want to move it into an organization.
 
-Not only does this move the repository along with all it's watchers and stars to another place, it also sets up a redirect from your URL to the new place. It will also redirect clones and fetches from Git, not just web requests.
+Not only does this move the repository along with all its watchers and stars to another place, it also sets up a redirect from your URL to the new place. It will also redirect clones and fetches from Git, not just web requests.

book/06-github/sections/5-scripting.asc

@@ -2,7 +2,7 @@
 
 So now we've covered all of the major features and workflows of GitHub, but any large group or project will have customizations they may want to make or external services they may want to integrate.
 
-Luckily for us, GitHub is really quite hackable in many ways. In this section we'll cover how to use the GitHub hooks system and it's API to make GitHub work how we want it to.
+Luckily for us, GitHub is really quite hackable in many ways. In this section we'll cover how to use the GitHub hooks system and its API to make GitHub work how we want it to.
 
 ==== Hooks
 

book/07-git-tools/sections/bundling.asc

@@ -3,7 +3,7 @@
 
 Though we've covered the common ways to transfer Git data over a network (HTTP, SSH, etc), there is actually one more way to do so that is not commonly used but can actually be quite useful.
 
-Git is capable of ``bundling'' it's data into a single file. This can be useful in various scenarios. Maybe your network is down and you want to send changes to your co-workers. Perhaps you're working somewhere offsite and don't have access to the local network for security reasons. Maybe your wireless/ethernet card just broke.  Maybe you don't have access to a shared server for the moment, you want to email someone updates and you don't want to transfer 40 commits via `format-patch`.
+Git is capable of ``bundling'' its data into a single file. This can be useful in various scenarios. Maybe your network is down and you want to send changes to your co-workers. Perhaps you're working somewhere offsite and don't have access to the local network for security reasons. Maybe your wireless/ethernet card just broke.  Maybe you don't have access to a shared server for the moment, you want to email someone updates and you don't want to transfer 40 commits via `format-patch`.
 
 This is where the `git bundle` command can be helpful. The `bundle` command will package up everything that would normally be pushed over the wire with a `git push` command into a binary file that you can email to someone or put on a flash drive, then unbundle into another repository.
 

book/07-git-tools/sections/replace.asc

@@ -1,7 +1,7 @@
 [[_replace]]
 === Replace
 
-Git's objects are unchangeable, but it does provide an interesting way to pretend to replace objects in it's database with other objects.
+Git's objects are unchangeable, but it does provide an interesting way to pretend to replace objects in its database with other objects.
 
 The `replace` command lets you specify an object in Git and say "every time you see this, pretend it's this other thing". This is most commonly useful for replacing one commit in your history with another one.
 

book/07-git-tools/sections/signing.asc

@@ -142,7 +142,7 @@ Date:   Wed Jun 4 19:49:17 2014 -0700
     signed commit
 ----
 
-Additionally, you can configure `git log` to check any signatures it finds and list them in it's output with the `%G?` format.
+Additionally, you can configure `git log` to check any signatures it finds and list them in its output with the `%G?` format.
 
 [source,console]
 ----

book/07-git-tools/sections/submodules.asc

@@ -608,7 +608,7 @@ $ git commit -m "Merge Tom's Changes" <5>
 It can be a bit confusing, but it's really not very hard.
 
 Interestingly, there is another case that Git handles.
-If a merge commit exists in the submodule directory that contains **both** commits in it's history, Git will suggest it to you as a possible solution. It sees that at some point in the submodule project, someone merged branches containing these two commits, so maybe you'll want that one.
+If a merge commit exists in the submodule directory that contains **both** commits in its history, Git will suggest it to you as a possible solution. It sees that at some point in the submodule project, someone merged branches containing these two commits, so maybe you'll want that one.
 
 This is why the error message from before was ``merge following commits not found'', because it could not do *this*. It's confusing because who would expect it to **try** to do this?
 

book/09-git-and-other-scms/sections/client-tfs.asc

@@ -408,5 +408,5 @@ If you want to work on the newly-minted branch, you'll want to base your new com
 
 Git-tf and Git-tfs are both great tools for interfacing with a TFVC server.
 They allow you to use the power of Git locally, avoid constantly having to round-trip to the central TFVC server, and make your life as a developer much easier, without forcing your entire team to migrate to Git.
-If you're working on Windows (which is likely if your team is using TFS), you'll probably want to use git-tfs, since it's feature set is more complete, but if you're working on another platform, you'll be using git-tf, which is more limited.
+If you're working on Windows (which is likely if your team is using TFS), you'll probably want to use git-tfs, since its feature set is more complete, but if you're working on another platform, you'll be using git-tf, which is more limited.
 As with most of the tools in this chapter, you should choose one of these version-control systems to be canonical, and use the other one in a subordinate fashion – either Git or TFVC should be the center of collaboration, but not both.

book/C-git-commands/1-git-commands.asc

@@ -88,9 +88,9 @@ Finally, we emulate it at a low level in <<_tree_objects>>, so you can get an id
 
 ==== git status
 
-The `git status` command will show you the different states of files in your working directory and staging area. Which files are modified and unstaged and which are staged but not yet committed. In it's normal form, it also will show you some basic hints on how to move files between these stages.
+The `git status` command will show you the different states of files in your working directory and staging area. Which files are modified and unstaged and which are staged but not yet committed. In its normal form, it also will show you some basic hints on how to move files between these stages.
 
-We first cover `status` in <<_checking_status>>, both in it's basic and simplified forms. While we use it throughout the book, pretty much everything you can do with the `git status` command is covered there.
+We first cover `status` in <<_checking_status>>, both in its basic and simplified forms. While we use it throughout the book, pretty much everything you can do with the `git status` command is covered there.
 
 ==== git diff
 
@@ -164,7 +164,7 @@ There are just a handful of commands that implement most of the branching and me
 
 The `git branch` command is actually something of a branch management tool. It can list the branches you have, create a new branch, delete branches and rename branches.
 
-Most of <<_git_branching>> is dedicated to the `branch` command and it's used throughout the entire chapter. We first introduce it in <<_create_new_branch>> and we go through most of it's other features (listing and deleting) in <<_branch_management>>.
+Most of <<_git_branching>> is dedicated to the `branch` command and it's used throughout the entire chapter. We first introduce it in <<_create_new_branch>> and we go through most of its other features (listing and deleting) in <<_branch_management>>.
 
 In <<_tracking_branches>> we use the `git branch -u` option to set up a tracking branch.
 
@@ -180,7 +180,7 @@ We see how to use it to start tracking branches with the `--track` flag in <<_tr
 
 We use it to reintroduce file conflicts with `--conflict=diff3` in <<_checking_out_conflicts>>.
 
-We go into closer detail on it's relationship with `git reset` in <<_git_reset>>.
+We go into closer detail on its relationship with `git reset` in <<_git_reset>>.
 
 Finally, we go into some implementation detail in <<_the_head>>.