From 4c68bc89f7ac0fbd2c0656f37e1c02f3ddb02824 Mon Sep 17 00:00:00 2001
From: Skylar Ray <137945430+sky-coderay@users.noreply.github.com>
Date: Fri, 15 Nov 2024 20:23:43 +0200
Subject: [PATCH] Update RELEASE.md

---
 RELEASE.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/RELEASE.md b/RELEASE.md
index 5e2182e995f..98df536a472 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -10,7 +10,7 @@ The `major` version has to be increased as soon as a breaking change is introduc
 
 ### Minor
 
-The `minor` is increased as soon as new smaller features do get introduced. A `minor` release will not affect any depending project. Such a release only introduces smaller enhancements and features a project could use.
+The `minor` is increased as soon as new smaller features get introduced. A `minor` release will not affect any depending project. Such a release only introduces smaller enhancements and features a project could use.
 
 ### Patch
 
@@ -36,7 +36,7 @@ Further details about versioning can be found in the [semver 2.0.0 specification
     - `bumped-version` of release branch should be of main web3 package.
 3. `yarn`: Verify all dependencies have been installed
 4. Bump packages version numbers using `lerna version --no-push --no-private --no-git-tag-version` . This will update package versions and also run lifecycle scripts.
-    - It will prompt for new version , modify package metadata and run life cycle scripts (in our case `version`), for bootstrapping lerna will use underlying yarn.
+    - It will prompt for new version , modify package metadata and run lifecycle scripts (in our case `version`), for bootstrapping lerna will use underlying yarn.
 5. Update each package's and also root `CHANGELOG.md`: 
 
     5.A. If there are any changes in package during release PR e.g. dependency updated that effects package, add entry in changelog under `## [Unreleased]` of that package's changelog.