docs: fix "re-using"/"re-used" typo in sqlx-core doc comments#4239
Draft
Bojun-Vvibe wants to merge 1 commit intolaunchbadge:mainfrom
Draft
docs: fix "re-using"/"re-used" typo in sqlx-core doc comments#4239Bojun-Vvibe wants to merge 1 commit intolaunchbadge:mainfrom
Bojun-Vvibe wants to merge 1 commit intolaunchbadge:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Repo: launchbadge/sqlx (⭐ 13000)
Type: docs
Files changed: 3
Lines: +3/-3
What
Replaces the hyphenated spellings "re-using" / "re-used" with the canonical
single-word forms "reusing" / "reused" in three sqlx-core doc comments
(
encode.rs,pool/mod.rs,statement.rs). Detected viacodespell.Why
codespellflags these as misspellings and the standard English form isunhyphenated. Doc comments here are surfaced on docs.rs as part of the
public API docs, so polishing them improves the reader experience at no
risk to runtime behavior.
Testing
Pure documentation comment edits — no behavior change.
cargo docwouldstill build;
codespell sqlx-core/srcno longer reports these three sites.Risk
Low — comment-only changes in public-facing docs.