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

Fix spelling mistakes and typos #362

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

Danyylka
Copy link

This pull request addresses various spelling and consistency issues across the documentation. The following corrections were made:

"checkout" has been changed to "check out" for proper usage in context.
"pull request" is now capitalized as "Pull Request" for consistency with standard terminology.
"EVM compatible" is corrected to "EVM-compatible" to reflect the correct hyphenation.
"non EVM" is updated to "non-EVM" for correct formatting and clarity.
"ERC721" and "ERC1155" have been corrected to "ERC-721" and "ERC-1155" to properly match the official standards.
"read more about pricing" has been modified to "read more about the pricing" to improve clarity and grammar.
"self-soverign" has been corrected to "self-sovereign" for accurate spelling.

I have fixed the issue by adding the missing hyphens, changing ERC721 to ERC-721 and ERC1155 to ERC-1155.
"compatible" should be written with a hyphen as "EVM-compatible" because it is a compound adjective describing the type of chains.

"non EVM" should be written with a hyphen as "non-EVM" because it is a compound adjective.
I have corrected the spelling error by changing "soverign" to "sovereign."
"checkout" → "check out"
In this context, "check out" should be written with a space, as it is a phrasal verb.

"create a pull request" → "create a Pull Request"
In documentation, it is common to capitalize the name of a process or specific action, such as Pull Request.
@Danyylka
Copy link
Author

Danyylka commented Dec 6, 2024

Hi team! Could someone please review and merge my pull request? Let me know if any changes are needed. Thanks!
@makoto
@Arachnid
@ligi
@jthomerson

@Danyylka
Copy link
Author

@gskril @makoto Could you please review my corrections?

I hope I was able to help in some way. Thank you for your work.

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.

1 participant