Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed a typo in the "Release Process" section of the documentation. #7463

Open
wants to merge 1 commit into
base: 4.x
Choose a base branch
from

Conversation

savvar9991
Copy link

Fix typo: "effects" -> "affects" in release guidelines

The original sentence read:
"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."
The updated sentence now reads:
"5.A. If there are any changes in package during release PR e.g. dependency updated that affects package, add entry in changelog under ## [Unreleased] of that package's changelog."

The_ typo could confuse readers unfamiliar with the intended meaning, as "effects" (meaning outcomes or results) is incorrect in this context. "Affects" (meaning influences or impacts) is the appropriate term, aligning with the technical intent of the sentence. This correction enhances the readability and professionalism of the documentation, which is critical for developers following the release process.

Copy link
Contributor

@jdevcs jdevcs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contributions. we are in the process of sunsetting Web3.js, Our focus during this transition will be on addressing only critical issues to ensure a smooth migration for our users.
For further details regarding the sunsetting of Web3.js, please refer to the official announcement here: Web3.js Sunset Announcement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants