commit - dbe7aff963cbe2ce4b9c3371fe6c11175109412e
commit + c6e561acfdcb8a143e7814ef18476392dde89a22
blob - db76c7290057afc8422f57e319b1814cdf5e6136
blob + bfd7e4ff83a3eed3e065093004d4f431966f72db
--- posts/git-auto-deploy.md
+++ posts/git-auto-deploy.md
@@ -10,7 +10,7 @@ So I thought it would be best to document my full proc
 
 ## Before We Begin
 
-This "tutorial" assumes that you already have a `git` server setup. It shouldn't matter what kind of forge your using, so long as you have access to the `hooks/` directory and have the ability to write a custom `post-receive` script.
+This "tutorial" assumes that you already have a `git` server setup. It shouldn't matter what kind of forge you're using, so long as you have access to the `hooks/` directory and have the ability to write a custom `post-receive` script.
 
 For my purposes I will be running standard `git` via the web through `cgit`, hosted on NearlyFreeSpeech (FreeBSD based).
 
@@ -67,7 +67,7 @@ done
 
 Let's break everything down.
 
-First we check if the branch being pushed to the remote server is `master`. Only if this is true do we proceed. (Feel free to change this if your prefer something like `production` or `deploy`)
+First we check if the branch being pushed to the remote server is `master`. Only if this is true do we proceed. (Feel free to change this if you prefer something like `production` or `deploy`)
 
 ~~~bash
 if [ "$branch" == "master" ]; then