-
Notifications
You must be signed in to change notification settings - Fork 50
Fix typos #479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix typos #479
Conversation
WalkthroughA series of minor typographical and grammatical corrections were made across various documentation files and a configuration file comment. No functional, structural, or content changes were introduced; all updates are limited to spelling and punctuation improvements. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Pre-Merge Checks (1 passed, 2 warnings)❌ Failed Checks (2 warnings)
✅ Passed Checks (1 passed)
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (4)
docs/reference/configuration.md (3)
302-308
: Two typos still present in the bullet list.
managemet
→management
trakcer
→tracker
- You use the built-in issue managemet system of GitHub or GitLab. + You use the built-in issue management system of GitHub or GitLab. - and [Let CodeRabbit read your issue trakcer](https://docs.coderabbit.ai/guides/setup-best-practices#issues). + and [Let CodeRabbit read your issue tracker](https://docs.coderabbit.ai/guides/setup-best-practices#issues).
910-914
: Missed typo: “reposistory”- and JavaScript files in a reposistory's `src` directory: + and JavaScript files in a repository's `src` directory:
1399-1403
: Missed typo: “reposiorty’s”- than the reposiorty's main branch (usually `main` or `master`.) + than the repository's main branch (usually `main` or `master`.)docs/guides/custom-reports.md (1)
310-313
: Still-misspelled word and brand capitalization“thourhg” is still misspelled and the product name should remain “CodeRabbit”.
-Do not enable this option unless you have asked coderabbit to create a "Score Card" thourhg a comment or implemented the "Score Chart" bot comment flow below. -For example you can ask coderabbit to check several conditions on a pull request and produce a "Score Chart": +Do not enable this option unless you have asked CodeRabbit to create a "Score Card" through a comment or implemented the "Score Chart" bot comment flow below. +For example you can ask CodeRabbit to check several conditions on a pull request and produce a "Score Chart":
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
docs/changelog.md
(1 hunks)docs/faq.md
(1 hunks)docs/guides/custom-reports.md
(2 hunks)docs/guides/ondemand-reports.md
(1 hunks)docs/guides/reports-overview.md
(1 hunks)docs/guides/setup-best-practices.md
(1 hunks)docs/reference/configuration.md
(3 hunks)tailwind.config.js
(1 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings
Learnt from: NatoBoram
PR: coderabbitai/coderabbit-docs#165
File: docs/finishing-touches/docstrings.md:9-9
Timestamp: 2024-12-05T21:29:59.510Z
Learning: The link `/future-developments#finishing-touches` in `docs/finishing-touches/docstrings.md` is correct and should not be flagged as incorrect in future reviews.
docs/guides/setup-best-practices.md (2)
Learnt from: NatoBoram
PR: #165
File: docs/finishing-touches/docstrings.md:9-9
Timestamp: 2024-12-05T21:29:59.510Z
Learning: The link /future-developments#finishing-touches
in docs/finishing-touches/docstrings.md
is correct and should not be flagged as incorrect in future reviews.
Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#0
File: :0-0
Timestamp: 2025-06-02T14:07:49.512Z
Learning: For files in docs/tools/*.md directory: Do not recommend installation instructions or usage setup steps. All tools documented in this directory are pre-installed in CodeRabbit's default environment and require no installation steps from users. Documentation should focus on tool capabilities and features only.
docs/faq.md (2)
Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.
Learnt from: NatoBoram
PR: #165
File: docs/finishing-touches/docstrings.md:9-9
Timestamp: 2024-12-05T21:29:59.510Z
Learning: The link /future-developments#finishing-touches
in docs/finishing-touches/docstrings.md
is correct and should not be flagged as incorrect in future reviews.
docs/guides/custom-reports.md (1)
Learnt from: NatoBoram
PR: #165
File: docs/finishing-touches/docstrings.md:9-9
Timestamp: 2024-12-05T21:29:59.510Z
Learning: The link /future-developments#finishing-touches
in docs/finishing-touches/docstrings.md
is correct and should not be flagged as incorrect in future reviews.
docs/reference/configuration.md (4)
Learnt from: NatoBoram
PR: #165
File: docs/finishing-touches/docstrings.md:9-9
Timestamp: 2024-12-05T21:29:59.510Z
Learning: The link /future-developments#finishing-touches
in docs/finishing-touches/docstrings.md
is correct and should not be flagged as incorrect in future reviews.
Learnt from: guritfaq
PR: #21
File: docs/integrations/ast-grep.md:45-66
Timestamp: 2024-06-10T19:44:11.319Z
Learning: Always flag inconsistencies in the use of "sub-rule" or "subrule" for clarity and consistency in documentation related to "AST-Grep" integration.
Learnt from: guritfaq
PR: #21
File: docs/integrations/ast-grep.md:45-66
Timestamp: 2024-10-08T15:37:07.967Z
Learning: Always flag inconsistencies in the use of "sub-rule" or "subrule" for clarity and consistency in documentation related to "AST-Grep" integration.
Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#0
File: :0-0
Timestamp: 2025-06-02T14:07:49.512Z
Learning: For files in docs/tools/*.md directory: Do not recommend installation instructions or usage setup steps. All tools documented in this directory are pre-installed in CodeRabbit's default environment and require no installation steps from users. Documentation should focus on tool capabilities and features only.
🔍 MCP Research (2 servers)
Context7: - PR #479 fixes typographical errors across multiple documentation files and tailwind.config.js in the CodeRabbit docs repository without altering functionality or exported entities (#479).
- Specific typo corrections include "Avgerage" to "Average" in docs/changelog.md, missing apostrophe in docs/faq.md heading, and multiple spelling fixes in docs/guides and docs/reference/configuration.md.
- Estimated code review effort is low; changes improve documentation clarity and professionalism without impacting code or configuration.
Linear: ""
🔇 Additional comments (10)
tailwind.config.js (1)
24-24
: Typo fixed in inline comment – looks good
The correction from “settigns” to “settings” clarifies the purpose of the dark-mode hook without touching runtime behavior.docs/changelog.md (1)
253-253
: Spelling correction acknowledged
“Average” is now spelled correctly in the dashboard bullet list. No other issues spotted.docs/guides/ondemand-reports.md (1)
17-18
: Spelling fix verified
“benefits” is now correctly spelled; the surrounding guidance remains unchanged and coherent.docs/guides/reports-overview.md (1)
29-30
: Spelling fix verified
The same “benefits” typo has been corrected here for consistency across docs.docs/reference/configuration.md (3)
607-608
: Typo fixes look good.
subsequent
is now spelled correctly – thanks for the cleanup.
905-909
: Corrected “instructions” typo – LGTM.Both lines read smoothly after the fix.
932-934
: Minor spelling correction approved.
languages
now reads correctly.docs/guides/custom-reports.md (1)
106-110
: Spelling fix looks goodThe “durring → during” correction improves clarity.
docs/guides/setup-best-practices.md (1)
3-3
: Typo fixed – description reads wellNo further changes required.
docs/faq.md (1)
66-66
: Heading typo resolvedThe apostrophe addition is correct.
@kianmeng Appreciate you finding these typos and raising a PR! |
🥳 🥳 🥳 🥳 🥳 |
Found via
codespell -S pnpm-lock.yaml -L ned,sav,paket