Fix some linting issues and documentation errors

GitHooksToolbox · Feb 18, 2021 · 52aa640 · 52aa640
1 parent 4a3699f
commit 52aa640
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 6 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,15 +5,23 @@ All notable changes to this project will be documented in this file.
 
 This changelog was automatically generated using [Caretaker](https://github.com/DevelopersToolbox/caretaker) by [Wolf Software](https://github.com/WolfSoftware)
 
-### [Unreleased](https://github.com/GitToolbox/git-hook-multiplexer/compare/v0.1.1...HEAD)
+### [v0.1.2](https://github.com/GitToolbox/git-hook-multiplexer/compare/v0.1.1...v0.1.2)
 
-- Add a new travis job to run github-linguist for information only [`[head]`](https://github.com/GitToolbox/git-hook-multiplexer/commit/)
+> Released on February, 18th 2021
 
-### [v0.1.0](https://github.com/GitToolbox/git-hook-multiplexer/releases/v0.1.0)
+- Fix some linting issues and documentation errors [`[head]`](https://github.com/GitToolbox/git-hook-multiplexer/commit/)
+
+- Add a new travis job to run github-linguist for information only [`[4a3699f]`](https://github.com/GitToolbox/git-hook-multiplexer/commit/4a3699f8ba555c0433121e0a70aa600e257f2f71)
+
+### [v0.1.1](https://github.com/GitToolbox/git-hook-multiplexer/compare/v0.1.0...v0.1.1)
 
 > Released on February, 16th 2021
 
 - Minor cleanup to the code to bring it in line with our coding standards [`[177abb0]`](https://github.com/GitToolbox/git-hook-multiplexer/commit/177abb0a94d254313d19dcea3704a9dce56084fc)
 
+### [v0.1.0](https://github.com/GitToolbox/git-hook-multiplexer/releases/v0.1.0)
+
+> Released on February, 10th 2021
+
 - The initial commit [`[108a277]`](https://github.com/GitToolbox/git-hook-multiplexer/commit/108a277a368b6e0924663bf16c73dbef0abea46e)
 
diff --git a/README.md b/README.md
@@ -45,12 +45,12 @@ With that in mind we have developed a simple multiplexer script. This script wil
 
 You install the multiplexer as the required git hook, and when the hook fires it will then run all of the defined scripts in sequence for you.
 
-Using a pre-commit hook as an example, set the multiplexer to run as your pre-commit hook (see the section on `intalling the multiplexer`), and when you execute a `git commit` command the pre-commit hook will fire (be execute).
+Using a pre-commit hook as an example, set the multiplexer to run as your pre-commit hook (see the section on `installing the multiplexer`), and when you execute a `git commit` command the pre-commit hook will fire (be execute).
 
 The multipler will then look in the following location for the actual real scripts to execute:
 
 ```shell
-GIT_ROOT/hooks/pre-commit
+${GIT_ROOT}/hooks/pre-commit
 ```
 
 > If you install the multiplexer as a post-commit hook it will look for GIT_ROOT/hooks/post-commit instead etc. for any supported hook.

diff --git a/VERSION.txt b/VERSION.txt
@@ -1 +1 @@
-0.1.1
+0.1.2