From c0ef879b8c1f82217c9787d62105e7d28b18acfe Mon Sep 17 00:00:00 2001
From: Afanti <127061691+threewebcode@users.noreply.github.com>
Date: Wed, 20 Dec 2023 08:21:57 +0800
Subject: [PATCH] fix: rectify the typos in the docs

---
 docs/code_contribution_guidelines.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/code_contribution_guidelines.md b/docs/code_contribution_guidelines.md
index 79f03df65..90adc57cf 100644
--- a/docs/code_contribution_guidelines.md
+++ b/docs/code_contribution_guidelines.md
@@ -331,7 +331,7 @@ Examples of common patterns w.r.t commit structures within the project:
   * Project or package wide file renamings should be in their own commit.
   * Ideally if a new package/struct/sub-system is added in a PR, there should
     be a single commit which adds the new functionality, with follow up
-    induvidual commits that begin to intergrate the functionality within the
+    individual commits that begin to integrate the functionality within the
     codebase.
   * If a PR only fixes a trivial issue, such as updating documentation on a
     small scale, fix typos, or any changes that do not modify the code, the