From 969f8c2c5453a0b172bf6e410b570ab7e4d4f399 Mon Sep 17 00:00:00 2001
From: Elias Rad <146735585+nnsW3@users.noreply.github.com>
Date: Wed, 25 Sep 2024 13:58:47 +0300
Subject: [PATCH] Update release-management.md

---
 release-management.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/release-management.md b/release-management.md
index 20ac266987b..f356ff7a80b 100644
--- a/release-management.md
+++ b/release-management.md
@@ -19,7 +19,7 @@ Together with the team, the release manager will refine the list of issues and P
 More generally and a non-negligible part of the planning is to properly ensure that bugs, issues that weren't totally identified in the roadmap, and the roadmap issues are still being processed as they should.
 During this phase, **all the current project issues have to be assigned.**
 
-After the release planning each one of us has to specify the effort need for each issue (1 - 2 - 3 - 5 - 8 - 13)
+After the release planning each one of us has to specify the effort needed for each issue (1 - 2 - 3 - 5 - 8 - 13)
 
 ## Release planning - refinement meeting:
 This meeting happens a few days after the release planning meeting.