update: Fix link casing for coding style guide

Updated the link to the coding style guide to use the correct casing.

Author: XV02

.github/CONTRIBUTING.md

@@ -4,7 +4,7 @@ We love pull requests from everyone.
 
 When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
 
-Please note we have a [coding style guide](../docs/coding_style.md), please follow it in all your interactions with the project.
+Please note we have a [coding style guide](../docs/CODING_STYLE.md), please follow it in all your interactions with the project.
 
 1. Fork, then clone the repo
 
@@ -25,7 +25,7 @@ Please note we have a [coding style guide](../docs/coding_style.md), please foll
 
 __Some things that will increase the chance that your pull request is accepted__
 
-* Follow our [coding style guide](../docs/coding_style.md).
+* Follow our [coding style guide](../docs/CODING_STYLE.md).
 * Write a good commit message.
 
 # Branch Naming Conventions
@@ -99,4 +99,4 @@ The structure and design conventions are based mainly on the “Conventional Bra
 
 # Bibliography
 [1]	“Conventional Branch,” Conventional Branch, 2025. https://conventional-branch.github.io/ (accessed 2025).</br>
-[2]	“Conventional Commits,” Conventional Commits. https://www.conventionalcommits.org/en/v1.0.0/ (accessed 2025).
+[2]	“Conventional Commits,” Conventional Commits. https://www.conventionalcommits.org/en/v1.0.0/ (accessed 2025).