feat: Add conventional commits note to contributing.md

fix(documentation): Changes post review

fix(documentation): Change case for heading

fix(documentation): Change case for heading

CONTRIBUTING.md

@@ -26,6 +26,7 @@ Working on your first Pull Request? You can learn how from this *free* series [H
 - [Make Changes](#make-changes)
 - [Run The Test Suite](#run-the-test-suite)
 - [Squash Your Commits](#squash-your-commits)
+- [Commit Message](#commit-message)
 - [Creating A Pull Request](#creating-a-pull-request)
 - [Common Steps](#common-steps)
 - [How We Review and Merge Pull Requests](#how-we-review-and-merge-pull-requests)
@@ -271,6 +272,21 @@ If you have made more than one commit, then you will need to _squash_ your commi
 
 To do this, see [Squashing Your Commits](http://forum.freecodecamp.org/t/how-to-squash-multiple-commits-into-one-with-git/13231).
 
+### Commit Message
+When you commit your changes, please use conventional commit messages.
+
+The commit message should be structured as follows:
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer]
+```
+For help writing your commit message, execute `npm run commit` from the command line and the [commitizen](http://commitizen.github.io/cz-cli/) CLI tool will assist you in creating a conventional commit message.
+
+Learn more at [Conventional Commits](http://conventionalcommits.org).
+
 ### Creating A Pull Request
 
 #### What is a Pull Request?