📝 Update conventional commits example

Add some contents to the example of conventional commits

Author: farbodsaraf

git/commit-message-naming.md

@@ -30,13 +30,13 @@ Access right management is used to check proper authorization to access an API b
 
 ## Conventional Commits
 
-Commit messages **MAY** use [Conventional Commits](https://www.conventionalcommits.org/en/) format. It provides guidelines to create a better commit history log, making easier to have automated tasks around it (eg: automated changelogs). Commits would follow the format `<type>[optional scope]: <description>`, where `<type>` might be `feat`/`fix`/`chore`/`docs` etc and breaking changes are indicated on the beginning of the optional body or footer section. 
+Commit messages **MAY** use [Conventional Commits](https://www.conventionalcommits.org/en/) format. It provides guidelines to create a better commit history log, making easier to have automated tasks around it (e.g. automated changelogs). Commits would follow the format `<type>[optional scope]: <description>`, where `<type>` might be `feat`/`fix`/`chore`/`docs` etc. and breaking changes are indicated on the beginning of the optional body or footer section. 
 
 Example:
 ```
-feat(scope-etc): Short and descriptive commit message
+git commit -m "feat(survey): add nps survey to the home page
 
-BREAKING CHANGE: Details around the Breaking Change
+BREAKING CHANGE:  `survey` objects in xml file have been re-used in the global configurations.
 ```
 
 Please refer to [Conventional Commits docs](https://www.conventionalcommits.org/en/) for more details