fix: multiple typos of different importance #3117
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Airdrop farming, but a useful contribution. |
RomarQ
approved these changes
Dec 21, 2024
RomarQ
added
I5-documentation 📄
then why not merging :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request addresses various typos across multiple files. The corrections include changes to spelling, grammar, and phrasing to improve clarity and consistency throughout the codebase and documentation.
What does it do?
What important points reviewers should know?
Is there something left for follow-up PRs?
No additional work related to these changes is anticipated. This PR comprehensively addresses the identified typos.
What alternative implementations were considered?
No alternatives were necessary, as this PR strictly focuses on typo corrections and grammatical improvements.
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
None are directly related to these changes. The fixes are isolated to this repository.
What value does it bring to the blockchain users?
Although the changes are not directly user-facing, they improve codebase maintainability, readability, and developer experience, reducing potential confusion for contributors and maintainers.
Allow edits by maintainers
✔️ Checked.