aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2015-04-30 16:17:10 +1200
committerTom Ryder <tom@sanctum.geek.nz>2015-04-30 16:17:10 +1200
commite237ac1e4f2743849b69afc386c2161ed86ab536 (patch)
tree2acf76bf90176edf1900599e1dfbb4217840fcdb
parentFirst commit (diff)
downloadsyntax-checking-git-hooks-e237ac1e4f2743849b69afc386c2161ed86ab536.tar.gz
syntax-checking-git-hooks-e237ac1e4f2743849b69afc386c2161ed86ab536.zip
Monospace var name
-rw-r--r--README.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.markdown b/README.markdown
index ce4a3a2..aba7dab 100644
--- a/README.markdown
+++ b/README.markdown
@@ -4,7 +4,7 @@ Syntax checking Git hooks
As used by Tom Ryder, because Michael Fincham asked.
The `pre-commit` file goes in `.git/hooks` in your repository, and you make it
-executable. You'll need `file(1)` and various other binaries in your PATH.
+executable. You'll need `file(1)` and various other binaries in your `PATH`.
This is nowhere near as tidy as it could be, but it correctly handles syntax
checking and linting of added or changed files only, without rescanning the