summaryrefslogtreecommitdiff
path: root/wiki/git
diff options
context:
space:
mode:
authorOwen Jacobson <owen.jacobson@grimoire.ca>2013-09-19 17:00:41 -0400
committerOwen Jacobson <owen.jacobson@grimoire.ca>2013-09-19 17:00:41 -0400
commit2efe24ca8af0a5e2938b4a7ed06d54ffc481a2da (patch)
treee0425b3f00e4fe0cb400308a68b710dc89efb6f3 /wiki/git
parentc40c53873b7da5423db9cc1b2453231a034b9385 (diff)
Spell-o (thanks, @SurprisingEdge!)
Diffstat (limited to 'wiki/git')
-rw-r--r--wiki/git/stop-using-git-pull-to-deploy.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/git/stop-using-git-pull-to-deploy.md b/wiki/git/stop-using-git-pull-to-deploy.md
index f6878fb..b9021bb 100644
--- a/wiki/git/stop-using-git-pull-to-deploy.md
+++ b/wiki/git/stop-using-git-pull-to-deploy.md
@@ -69,7 +69,7 @@ Sitaram's own documentation talks about how to accomplish these when
impractical) in most cases; deployment should use a dedicated clone of the
canonical repository.
-I also disaree with point 3, preferring to keep deployment-related changes
+I also disagree with point 3, preferring to keep deployment-related changes
outside of tracked files. This makes it much easier to argue that the changes
introduced to configure the project for deployment do not introduce new bugs
or other surprise features.