aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2024-09-20 10:51:26 -0400
committerBradley Taunt <bt@btxx.org>2024-09-20 10:51:26 -0400
commitc6e561acfdcb8a143e7814ef18476392dde89a22 (patch)
tree216579577ebbb9eed5811e7a457a50d00bd9486a
parentdbe7aff963cbe2ce4b9c3371fe6c11175109412e (diff)
Fix grammar mistakes in latest post
-rw-r--r--posts/git-auto-deploy.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/posts/git-auto-deploy.md b/posts/git-auto-deploy.md
index db76c72..bfd7e4f 100644
--- a/posts/git-auto-deploy.md
+++ b/posts/git-auto-deploy.md
@@ -10,7 +10,7 @@ So I thought it would be best to document my full process. These notes are more
## 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