From c0d6f1eebb309639718961ba7bbd5e94d759ef3d Mon Sep 17 00:00:00 2001
From: Durgesh <84910181+Durgesh-babu@users.noreply.github.com>
Date: Sat, 31 Jan 2026 20:05:48 +0530
Subject: [PATCH] docs: fix typo in PR general instructions from "live" to
 "leave" in Rule 8 for clarity.

---
 .../development/pr-general-instructions-and-handling.md         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/departments-operations/research-and-development/engineering/development/pr-general-instructions-and-handling.md b/departments-operations/research-and-development/engineering/development/pr-general-instructions-and-handling.md
index 6920c0e..97db134 100644
--- a/departments-operations/research-and-development/engineering/development/pr-general-instructions-and-handling.md
+++ b/departments-operations/research-and-development/engineering/development/pr-general-instructions-and-handling.md
@@ -77,7 +77,7 @@ Feature Branch will allow PR to have multiple checks and is expected to reduce b
 
 ### Rule 8: Comments to Code
 
-As we are an open source company with potential for every PR to be checked by community and have multiple engineers from different areas that can review your code it helps a lot to live comments on code to place lines of thought, as a calculation memory.
+As we are an open source company with potential for every PR to be checked by community and have multiple engineers from different areas that can review your code it helps a lot to leave comments on code to place lines of thought, as a calculation memory.
 
 ### Rule 9: PR Review Actions