Fixing various phrasing inconsistencies and spelling errors in prev PR's comments #193
Conversation
This file contains hidden or 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
|
Thanks for these fixes! Unfortunately, CI has failed due to nightly changes. I've opened #194 to fix them, but it seems it fails to build due to a linker error. We'll have to wait until a newer Rust nightly version is released. |
|
@avirule CI should be fine now. Could you rebase on the latest |
|
Thanks! |
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.
Motivation
My previously merged pull request's code comments had various spelling errors, phrasing inconsistencies, and generally bothered me with their quality—I've gone back and edited them so they match the quality I'd expect from a public crate.
Changes
All I've edited are code comments that were made for code in my previous pull request.