Fix few typos in CONTRIBUTING.md

CONTRIBUTING.md

@@ -1,12 +1,13 @@
 # Contributing guidelines for TT-Forge
 
 ## PR Guidelines
+
 ### Community contributions
-Thank you for your interest in the TT-Forge project we appreciate your support.
+Thank you for your interest in the TT-Forge project, we appreciate your support.
 For all PRs we have an internal policy listed below which your PR will go through after an initial review has been done.
 
-The initial review will encompase the following:
-* Review the PR for CI / CD Readiness. Includes making sure that the code and PR at a high level makes sense for the project.
+The initial review will encompass the following:
+* Reviewing the PR for CI / CD Readiness, making sure that the code and PR at a high level make sense for the project.
 * Once approved for CI / CD readiness a Tenstorrent developer will kick off our CI/CD pipeline on your behalf.
 
 ### Internal contributions
@@ -16,11 +17,10 @@ For internal contributions we have the following guidelines:
 
 In addition to the 24 hour rule the following prerequisites for landing PR exist:
 * At least 1 reviewer signs off on the change
-* Component owner sign offs (github will tell you if this hasn't been met)
+* Component owners sign offs (github will tell you if this hasn't been met)
 * Green CI
 * Wait at least 24 hours since opening the PR to give all tagged reviewers a chance to take a look.  Or at least comment on the issue that they need more time to review.
   * *Rebasing or further changes to the PR do not reset the 24 hour counter.*
 
 ### Coding Guidelines and Standards
-
 Before submitting your PR, ensure your code adheres to the project’s [Coding Guidelines and Standards](./docs/src/coding-guidelines.md). These guidelines outline expectations for code style, formatting, and best practices to maintain consistency and quality across the project.