Fix Typos #13110
Closed
Fix Typos #13110
+7
−7
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 farmer detected, PR rejected |
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:
Fixed typo: emplimented to implemented
Fixed typo: debian to debain
Corrected capitalization: eips to EIPs
Fixed typo: and to an
Fixed typo: conect to connect
Fixed typo: entites to entities
Fixed typo: Indivates to Indicates
Fixing these errors is useful for several reasons:
Improved Readability and Professionalism: Correct spelling and capitalization make the document more professional and easier to read, enhancing the overall user experience.
Consistency: Using the correct capitalization for terms like ERC721 and EIPs ensures consistency across the project, making it easier for new contributors to follow along.
Searchability: Correctly spelled terms make the project easier to search, whether it's searching through code, documentation, or other resources.
Avoiding Confusion: Fixing spelling errors (like "conect" to "connect") ensures that users or developers do not misunderstand terms, which can be crucial in technical contexts.