Open
Conversation
This fixes a (very small) typo in the docs for `cargo-yank`. Specifically, since "unintentional SemVer breakages" is plural, the "an" that was at the beginning of that sentence was incorrect.
rustbot
added
A-documenting-cargo-itself
Collaborator
|
r? @ehuss rustbot has assigned @ehuss. Use Why was this reviewer chosen?The reviewer was selected based on:
|
Contributor
|
You'll need to run: cargo build-man
SNAPSHOTS=overwrite cargo testand amend your commit with the result to pass CI |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This fixes a (very small) typo in the docs for
cargo-yank. Specifically, since "unintentional SemVer breakages" is plural, the "an" that was at the beginning of that sentence was incorrect.What does this PR try to resolve?
There wasn't an issue, just a very tiny typo
How to test and review this PR?
Hopefully this shouldn't need any testing... it's just a change to a markdown file