Skip to content

fix: correct spelling errors across codebase#5403

Merged
nobodyiam merged 1 commit intoapolloconfig:masterfrom
RooobinYe:fix/typo-corrections-5402
Jun 5, 2025
Merged

fix: correct spelling errors across codebase#5403
nobodyiam merged 1 commit intoapolloconfig:masterfrom
RooobinYe:fix/typo-corrections-5402

Conversation

@RooobinYe
Copy link
Member

@RooobinYe RooobinYe commented Jun 5, 2025

What's the purpose of this PR

  • Fix 'chanage' to 'change' in documentation
  • Fix 'releated' to 'related' in changelog
  • Fix 'useable' to 'usable' in deployment guide
  • Fix 'applys' to 'applies' in webhook documentation
  • Fix 'commited' to 'committed' in JavaScript code

我才发现 wapper 也许不是一个拼写错误

Which issue(s) this PR fixes:

Fixes #5402

Brief changelog

Resolves issue #5402

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Read the Contributing Guide before making this pull request.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit tests to verify the code.
  • Run mvn clean test to make sure this pull request doesn't break anything.
  • Update the CHANGES log.

Summary by CodeRabbit

  • Bug Fixes

    • Corrected spelling errors in user interface elements to improve clarity.
  • Documentation

    • Fixed typographical errors in release notes and various documentation files for improved readability and professionalism.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 5, 2025

Walkthrough

This change corrects multiple spelling errors across source code, documentation, and comments. Terms such as "commited," "chanage," "releated," "useable," and "applys" are fixed to their correct forms. No functional, logical, or structural changes are introduced beyond these typographical corrections.

Changes

File(s) Change Summary
apollo-portal/src/main/resources/static/scripts/directive/namespace-panel-directive.js Fixed spelling of property "commited" to "committed" in three places.
changes/changes-1.9.0.md Corrected "community releated contents" to "community related contents".
docs/en/deployment/third-party-tool-rainbond.md Corrected "useable" to "usable" in documentation.
docs/en/extension/portal-how-to-enable-webhook-notification.md Corrected "applys" to "applies" in a JSON comment.
docs/scripts/multiple-language-redirect.js Corrected "chanage" to "change" in a comment.

Assessment against linked issues

Objective Addressed Explanation
Correct spelling mistakes: chanage, releated, useable, applys, commited (#5402)

Suggested labels

size:XS

Suggested reviewers

  • hezhangjian

Poem

A rabbit hopped in with a spelling fix,
Tweaked some letters, quick as a whisk.
"Committed" now spelled just right,
"Related" and "usable" shining bright.
Docs and scripts, all error-free,
Hippity-hop, what joy to see! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6541589 and 52e30f5.

📒 Files selected for processing (5)
  • apollo-portal/src/main/resources/static/scripts/directive/namespace-panel-directive.js (2 hunks)
  • changes/changes-1.9.0.md (1 hunks)
  • docs/en/deployment/third-party-tool-rainbond.md (1 hunks)
  • docs/en/extension/portal-how-to-enable-webhook-notification.md (1 hunks)
  • docs/scripts/multiple-language-redirect.js (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • docs/scripts/multiple-language-redirect.js
  • docs/en/extension/portal-how-to-enable-webhook-notification.md
🚧 Files skipped from review as they are similar to previous changes (3)
  • docs/en/deployment/third-party-tool-rainbond.md
  • changes/changes-1.9.0.md
  • apollo-portal/src/main/resources/static/scripts/directive/namespace-panel-directive.js
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build (8)
✨ Finishing Touches
  • 📝 Generate Docstrings

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 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.

@RooobinYe RooobinYe marked this pull request as ready for review June 5, 2025 09:21
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Jun 5, 2025
Copy link
Member

@spaceluke spaceluke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jun 5, 2025
Copy link
Member

@nobodyiam nobodyiam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

- Fix 'chanage' to 'change' in documentation
- Fix 'releated' to 'related' in changelog
- Fix 'useable' to 'usable' in deployment guide
- Fix 'applys' to 'applies' in webhook documentation
- Fix 'commited' to 'committed' in JavaScript code

我才发现 `wapper` 也许不是一个拼写错误

Resolves apolloconfig#5402
@nobodyiam nobodyiam force-pushed the fix/typo-corrections-5402 branch from 6541589 to 52e30f5 Compare June 5, 2025 12:57
@nobodyiam nobodyiam merged commit 75492b4 into apolloconfig:master Jun 5, 2025
10 of 11 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jun 5, 2025
@nobodyiam nobodyiam added this to the 2.5.0 milestone Feb 19, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm This PR has been approved by a maintainer size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

doc: multiple spelling errors were found

3 participants

Comments