docs: multiple typographical and grammatical errors across several files #335
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
sjoerdzwan
changed the title
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
query.md:Fixed a typo from "prick" to "price" in the description of the query functions. This change eliminates the confusion related to querying price data.
query.md:Removed an unnecessary semicolon in the "Parameters" heading, restoring proper formatting and ensuring uniformity across the section.
type-conventions.md:Changed "converted" to "converting" for more accurate contextual usage in the TypeScript Library description.
Corrections in
fees.md:Replaced "fo" with "for" to fix a typographical error.
Modified "as reward" to "as a reward" for grammatical correctness.
Grammar fix in
swaps.md:Corrected "When" to "when" for proper sentence structure, aligning it with the style used throughout the documentation.
These changes making docs more understandable and error-free for developers.
Does it close a specific issue?
Example:
Closes #336
Contribution
I have followed the Development Workflow
I have read the CODE OF CONDUCT
I HAVE MADE SURE TO ALLOW MAINTAINERS TO EDIT THIS PULL REQUEST
I have synced my fork so that it is up to date with the latest changes
Let us know your wallet address/ENS: