From 2d1bb41d0ca66c027f5856c76cf149c15bc073a7 Mon Sep 17 00:00:00 2001
From: Tomáš Znamenáček
Date: Fri, 12 Aug 2016 11:53:26 +0200
Subject: Link to a commit message writing guide

---
 CONTRIBUTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 70fa9c1..39cb20e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -4,7 +4,7 @@ Please note that this framework supports older OS X versions down to 10.6. When
 
 # Commit Messages
 
-Please use descriptive commit message. As an example, _Bug fix_ commit message doesn’t say much, while _Fixed a memory-management bug in formatting code_ works much better.
+Please use descriptive commit message. As an example, _Bug fix_ commit message doesn’t say much, while _Fix a memory-management bug in formatting code_ works much better. A [nice detailed article about writing commit messages](http://chris.beams.io/posts/git-commit/) is also available.
 
 # How to Release a New Version
 
@@ -26,4 +26,4 @@ Now push both the commits and tags (`--tags`) to GitHub and push the new podspec
 
 This will run sanity checks on the podspec and fail if the spec does not validate.
 
-That’s it. Go have a beer or a cup of tea to celebrate.
\ No newline at end of file
+That’s it. Go have a beer or a cup of tea to celebrate.
-- 
cgit v1.2.3