chore: fix some typos in comment

[cuiweiyuan]

Motivation and context

fix some typos in comment

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have created a changelog fragment
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (see GitHub docs)
• I have increased versions of npm packages if it is necessary
  (cvat-canvas,
  cvat-core,
  cvat-data and
  cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

• Bug Fixes
  • Corrected typographical errors in comments and messages across various components, enhancing clarity.
  • Updated comments related to ingress configuration in the Helm chart for better understanding.

[coderabbitai]

Walkthrough

This pull request consists of minor typographical corrections across multiple files in the CVAT (Computer Vision Annotation Tool) project. The changes include fixing spelling errors in comments and messages within TypeScript source files and a Helm chart values file. These corrections do not impact the functional behavior of the code but improve readability and documentation precision.

Changes

File	Change Summary
cvat-core/src/annotations-actions/base-action.ts	Corrected "commiting" to "committing" in a comment
cvat-core/src/annotations-actions/base-shapes-action.ts	Updated message from "Commiting handled objects" to "Committing handled objects"
cvat-ui/src/utils/is-able-to-change-frame.ts	Fixed comment typo from "hovewer" to "however"
helm-chart/values.yaml	Added a space before an ingress configuration comment

Poem

🐰 Typos hop away, spelling takes flight
With each correction, words shine bright
A rabbit's keen eye spots each mistake
Polishing prose for clarity's sake
Committing changes with linguistic grace! 🔍

---

📜 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 2fd48c8 and f681f13.

📒 Files selected for processing (4)

• cvat-core/src/annotations-actions/base-action.ts (1 hunks)
• cvat-core/src/annotations-actions/base-shapes-action.ts (1 hunks)
• cvat-ui/src/utils/is-able-to-change-frame.ts (1 hunks)
• helm-chart/values.yaml (1 hunks)

✅ Files skipped from review due to trivial changes (4)

• cvat-core/src/annotations-actions/base-action.ts
• cvat-ui/src/utils/is-able-to-change-frame.ts
• cvat-core/src/annotations-actions/base-shapes-action.ts
• helm-chart/values.yaml

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.92%. Comparing base (2fd48c8) to head (f681f13).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #8868      +/-   ##
===========================================
+ Coverage    73.90%   73.92%   +0.02%     
===========================================
  Files          408      408              
  Lines        44108    44108              
  Branches      3986     3986              
===========================================
+ Hits         32597    32606       +9     
+ Misses       11511    11502       -9     

Components	Coverage Δ
cvat-ui	78.33% <100.00%> (-0.05%)	⬇️
cvat-server	70.16% <ø> (+0.07%)	⬆️

[zhiltsov-max]

Thank you for contributing into the project!