Skip to content

Fix wording in RELEASING.md for clarity and consistency #5539

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

Merged
merged 2 commits into from
Feb 28, 2025

Conversation

vipocenka
Copy link
Contributor

  • Removed unnecessary parentheses around the release-cycle link.
  • Replaced "ongoing and reliable" with "consistent and reliable" for better readability and accuracy.

PR Checklist

  • Tests (N/A)
  • Documentation
  • Changeset entry (N/A)

Copy link

changeset-bot bot commented Feb 27, 2025

⚠️ No Changeset found

Latest commit: e40d685

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@Amxx Amxx changed the base branch from master to typo-fixes February 28, 2025 14:12
@Amxx Amxx merged commit 3615b0f into OpenZeppelin:typo-fixes Feb 28, 2025
11 of 14 checks passed
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