Fix grammatical and spelling errors in documentation #521
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
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.
Changes
bindings/rust/build.rs
// Do no generate layout tests.// Do not generate layout tests.Reason: Corrected grammatical error by using proper negative form "do not" instead of incorrect "do no".
bindings/node.js/README.md
* Verify a KZG poof claiming that p(z) == y.* Verify a KZG proof claiming that p(z) == y.Reason: Fixed spelling error - "poof" to "proof" for technical accuracy.
bindings/java/README.md
structure and name according your OS.structure and name according to your OS.Reason: Added missing preposition "to" for grammatical correctness.
Summary
These changes improve documentation readability and professionalism by fixing grammatical and spelling errors. Proper technical terminology and grammar are important for maintaining high-quality documentation that is clear and accurate for all users.
The changes are minor text corrections that do not affect any functionality but make the documentation more polished and professional.