docs: remove duplicated word 'in' in forcats content - #10331
Open
chenlichao wants to merge 1 commit into
Open
chenlichao wants to merge 1 commit into
chenlichao wants to merge 1 commit into
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
1 participant
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.
Summary
Removes a duplicated word ("in in" → "in") in the forcats content file.
Change
roadmaps/r/content/forcats@WVgYRRNpsNXBnz7V9JX29.md— "…order categories appear in in plots and tables…" → "…order categories appear in plots and tables…"roadmaps/r-programming/content/forcats@WVgYRRNpsNXBnz7V9JX29.md— same duplicated word in the identical sentence.The two files share the same content paragraph, so the fix is applied to both.
Verification
masterin both files (git grep 'appear in in'on upstreammastermatched exactly these two locations).appear in inreturns no matches.git diff --checkis clean; diff is 2 files, 1 line each — documentation-only, no code changes.This is an intentionally tiny typo fix per the contribution guidelines ("Fixing Typos — make your changes in the roadmap markdown file and submit a PR").