docs: follow consistency (#408)

* make `CONTRIBUTING.md` have consistency and fix grammatical errors

Signed-off-by: okcoder1 <codershub.code@gmail.com>

Author: ok-coder1

.github/CONTRIBUTING.md

@@ -20,7 +20,7 @@ Please make sure you have checked all the following before submitting a new issu
 - If you found an existing issue, use the react feature to show you have the same problem or need the same feature. Don't post comments like +1.
 - Use the Bug & Feature Issue templates and provide all the required information.
 - Be as detailed as possible and include screenshots wherever possible. This will help reproduce your bug or understand your feature request.
-- Refer to our [AI policy](#ai-policy)
+- Refer to our [AI policy](#ai-policy).
 - Do not bump SnapX's version in conventional pull requests. Only release branches like `develop`, `alpha`, and `beta` can do that.
 
 ## Contributing Code
@@ -80,7 +80,8 @@ Each commit message consists of a **header**, a **body**, and a **footer**. The
 ></type>
 ```
 
-> Any line of the commit message cannot be longer than 100 characters!<br/> This allows the message to be easier to read on GitHub as well as in various Git tools.
+> Any line of the commit message cannot be longer than 100 characters! \
+> This allows the message to be easier to read on GitHub as well as in various Git tools.
 
 ##### Type
 
@@ -99,8 +100,8 @@ Must be one of the following:
 
 ##### Scope
 
-The scope could be anything that helps to specify the scope (or feature) that is changing.
-It is not required.
+The scope could be anything that helps to specify the scope (or feature) that is changing. \
+**It is not required.**
 
 Examples
 
@@ -117,19 +118,19 @@ Examples
 
 The subject contains a succinct description of the change:
 
-- use the imperative, present tense: "change" not "changed" nor "changes"
-- don't capitalize the first letter
-- no dot (.) at the end
+- Use the imperative, present tense: "change"; not "changed" nor "changes"
+- Don't capitalize the first letter
+- No dot (.) at the end
 
 ##### Body
 
-Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
+Just as in the **subject**, use the imperative, present tense: "change"; not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
 
 ##### Footer
 
 The footer should contain any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**, **Fixes**, or **Relates to**.
 
-> Breaking Changes are intended to be highlighted in the ChangeLog as changes that will require community users to modify their code after updating to a version that contains this commit.
+> Breaking Changes are intended to be highlighted in the CHANGELOG as changes that will require community users to modify their code after updating to a version that contains this commit.
 
 ##### Sample Commit messages
 
@@ -193,23 +194,23 @@ The version bump is automatically determined based on your commit messages. Here
 
 ### Contribution Guidelines
 
-- The `master` branch should always contain **stable and tested** code.
+- The `master` branch should always contain **stable and tested** code. \
   _Use Pull Requests for all features or bug fixes. Merge them only when ready._
 
-- Each bug fix, feature, or change should have **one commit** associated with it.
+- Each bug fix, feature, or change should have **one commit** associated with it. \
   _Avoid mixing multiple changes into a single commit._
 
-- All commits must follow [Conventional Commit](https://www.conventionalcommits.org/) format.
+- All commits must follow [Conventional Commit](https://www.conventionalcommits.org/) format. \
   _We accept the Angular flavor (e.g., `feat:`, `fix:`) and support semantic bump hints._
 
 ### AI policy
 
 Okay, so here's the thing:
 
-- **No GitHub issues generated by AI.**
+- **No GitHub issues generated by AI.** \
 It won't be merged if it was written by a chatbot. Only open issues if you truly comprehend the feature or bug you're describing.
 
-- **No "vibe coding"**
+- **No "vibe coding".** \
 Just because "it works on your machine" doesn't mean you should submit the code. It doesn't belong here if you can't explain what it does or why.
 
 AI-assisted coding is acceptable. Copilots, linters, refactors, and other tools that speed up your work are all great as long as *you* understand what's happening behind the scenes.