docs: enforce conventional commits use and remove redundant line

Signed-off-by: dharapandya85 <dharapandya@gmail.com>

Author: dharapandya85

CONTRIBUTING.md

@@ -6,7 +6,7 @@ Thank you for your interest in contributing to `patch-hub`! This document outlin
 
 1. [Code of Conduct](#code-of-conduct)
 2. [Getting Started](#getting-started)
-3. [Development Workflow](#development-workflow)
+3. [Development s](#development-workflow)
 4. [Coding Style](#coding-style)
 5. [Commit Guidelines](#commit-guidelines)
 6. [Pull Request Guidelines](#pull-request-guidelines)
@@ -119,9 +119,6 @@ Commit contents, in other words, the changes the commit introduce should:
 Example:
 feat(foo)!: introduce breaking change bar
 
-`patch-hub` follows the use of [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) wherein you indicate the type of change you're making at the start with a label, followed by a scope (optional, since the project is still small), and then the commit message after a colon. In case the commit is a breaking change, i.e it disrupts existing functionality, please use the `!` symbol before the `:` to indicate as such.
-
-
 Example Commits:
 - Breaking change that introduces a feature to `config`: `feat(config)!: allow provided config object to extend other configs`
 - Bug fix to patch parsing logic: `fix(patch): fix incorrect title in patches`