Skip to content

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

Merged
merged 2 commits into from
Jul 31, 2025
Merged

Fix typos #479

merged 2 commits into from
Jul 31, 2025

Conversation

kianmeng
Copy link
Contributor

Found via codespell -S pnpm-lock.yaml -L ned,sav,paket

Found via `codespell -S pnpm-lock.yaml -L ned,sav,paket`
Copy link
Contributor

coderabbitai bot commented Jul 30, 2025

Walkthrough

A 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

Cohort / File(s) Change Summary
Changelog Typo Fix
docs/changelog.md
Corrected "Avgerage" to "Average" in the Dashboard Redesign section.
FAQ Heading Correction
docs/faq.md
Added missing apostrophe in heading ("Whats" → "What's").
Custom Reports Typos
docs/guides/custom-reports.md
Fixed several spelling and grammar errors ("durring" → "during", etc.).
On-demand Reports Typo
docs/guides/ondemand-reports.md
Corrected "benifits" to "benefits".
Reports Overview Typo
docs/guides/reports-overview.md
Corrected "benifits" to "benefits".
Setup Guide Metadata Typo
docs/guides/setup-best-practices.md
Fixed "seting" to "setting" in the description metadata.
Configuration Reference Typos
docs/reference/configuration.md
Corrected multiple spelling errors ("repostory", "subsquent", etc.).
Tailwind Config Comment Typo
tailwind.config.js
Fixed comment typo ("settigns" → "settings").

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop, a skip, a typo gone,
The docs now shine, their errors withdrawn.
With every word now spelled just right,
This bunny beams with pure delight.
🐇✨

“No more ‘benifits’—just benefits here,
Our garden of docs is crystal clear!”

Pre-Merge Checks (1 passed, 2 warnings)

❌ Failed Checks (2 warnings)
Check Name Status Explanation Resolution
Title Check ⚠️ Warning The title 'Fix typos' is too generic and does not specify the scope or types of files affected by the changes. Revise the title to be more descriptive, for example: 'docs: correct typos in changelog, FAQ, guides, and reference docs'.
Description Check ⚠️ Warning The description only references the codespell command used and lacks details on which files were modified and what typos were fixed. Expand the pull request description to include a summary of the specific typo corrections and affected files, and add a pull request template to the repository to ensure consistent and complete descriptions.
✅ Passed Checks (1 passed)
Check Name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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.

managemetmanagement
trakcertracker

- 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

📥 Commits

Reviewing files that changed from the base of the PR and between a9bb694 and 773f43c.

📒 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 good

The “durring → during” correction improves clarity.

docs/guides/setup-best-practices.md (1)

3-3: Typo fixed – description reads well

No further changes required.

docs/faq.md (1)

66-66: Heading typo resolved

The apostrophe addition is correct.

@karan925 karan925 merged commit ebe72ce into coderabbitai:main Jul 31, 2025
3 checks passed
@karan925
Copy link
Collaborator

@kianmeng Appreciate you finding these typos and raising a PR!

@kianmeng
Copy link
Contributor Author

🥳 🥳 🥳 🥳 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy