Fixed the issue mentioned in pull request.

Author: bipenc

docs/git/branching_naming_convention.md

@@ -9,7 +9,6 @@ sidebar_label: Branch Naming Convention
 * Branch name should exactly match with the corresponding JIRA ticket that you will be working on. `<project-name>-<ticket-number>`
 
    Examples:
-
           * FHF-100
           * DEL-200
 

docs/git/smart_commit.md

@@ -4,13 +4,13 @@ title: Smart Commit
 sidebar_label: Smart Commit
 ---
 
-Smart commits allows a team to perform actions on Jira issues from a single commit.  Users can enter the issue key and the desired action such as time tracking or closing an issue.
+Smart commits allows a team to perform actions on JIRA issues from a single commit. Users can enter the issue key and the desired action such as time tracking or closing an issue.
 
 #### Some of the mostly used smart commands:
 
-* `#comment`:  Adds a comment to a Jira issue. `ISSUE_KEY #comment <your comment text>`
-* `#time` : Records time tracking information against a Jira issue.
-* `#<transition-name>` :  Moves the Jira issue to a particular workflow state.
+* `#comment`:  Adds a comment to a JIRA issue. `ISSUE_KEY #comment <your comment text>`
+* `#time` : Records time tracking information against a JIRA issue.
+* `#<transition-name>` :  Moves the JIRA issue to a particular workflow state.
 
 #### Examples: