📝 Improve Git Commit Messages section.

- Use why format for each sub section.
- Improve title for a better understanding.

Author: romsi

README.md

@@ -10,7 +10,10 @@ These guidelines are based on [Building a strong community Github documentation]
 	* [Multiple Issue Templates Over Single Issue Template](#multiple-issue-template-over-single-issue-template)
 	* [Issue & Pull Request Expectation](#issue--pull-request-expectation)
 	* [Promoting A High Contribution Quality](#promoting-a-high-contribution-quality)
-	* [Git Commit Messages](#git-commit-messages)
+* [Git Commit Messages](#git-commit-messages)
+	* [Short Commit Messages](#short-commit-messages)
+	* [Issue Reference](#issue-reference)
+	* [Commit Nature](#commit-nature)
 * [Milestone](#milestone)
 * [Label](#label)
 * [CHANGELOG](#changelog)
@@ -94,11 +97,11 @@ Templates should promote a high contribution quality by referring [contributing
 ...
 ```
 
-### Git Commit Messages
+## Git Commit Messages
 
-#### Content
+### Short Commit Messages
 
-Git Commit messages should always be clear about what has been done. It should be written at the present tense and imperative Mood.
+Git commit messages should help reviewers to quickly understand what has been done. It should be short, clear and written at the present tense and imperative mood.
 
 **Preferred:**
 ```markdown
@@ -112,9 +115,9 @@ Git Commit messages should always be clear about what has been done. It should b
 - Updates navigation storyboard.
 ```
 
-#### Reference
+### Issue Reference
 
-Git Commit messages should reference issues at the end.
+Referencing issue in git commit messages should help anyone to track progress on a specific issue. Git commit messages should always reference issues at the end.
 
 **Preferred:**
 ```markdown
@@ -128,23 +131,22 @@ Git Commit messages should reference issues at the end.
 - #1024 Remove unused ViewController method.
 ```
 
-#### Emojis
-
-For clear visual identification start the commit message with an applicable emoji:
-
-   - :art: `:art:` when improving the format/structure of the code
-   - :racehorse: `:racehorse:` when improving performance
-   - :non-potable_water: `:non-potable_water:` when plugging memory leaks
-   - :memo: `:memo:` when writing docs
-   - :bug: `:bug:` when fixing a bug
-   - :fire: `:fire:` when removing code or files
-   - :green_heart: `:green_heart:` when fixing the CI build
-   - :white_check_mark: `:white_check_mark:` when adding tests
-   - :lock: `:lock:` when dealing with security
-   - :arrow_up: `:arrow_up:` when upgrading dependencies
-   - :arrow_down: `:arrow_down:` when downgrading dependencies
-   - :shirt: `:shirt:` when removing linter warnings
-
+### Commit Nature
+
+Emojis should help reviewers to quickly and visually identify the nature of the commit. For clear visual identification start the commit message with an applicable emoji:
+
+- :art: `:art:` when improving the format/structure of the code
+- :racehorse: `:racehorse:` when improving performance
+- :non-potable_water: `:non-potable_water:` when plugging memory leaks
+- :memo: `:memo:` when writing docs
+- :bug: `:bug:` when fixing a bug
+- :fire: `:fire:` when removing code or files
+- :green_heart: `:green_heart:` when fixing the CI build
+- :white_check_mark: `:white_check_mark:` when adding tests
+- :lock: `:lock:` when dealing with security
+- :arrow_up: `:arrow_up:` when upgrading dependencies
+- :arrow_down: `:arrow_down:` when downgrading dependencies
+- :shirt: `:shirt:` when removing linter warnings
 
 ## Milestone