docs(grid): [grid]correct wrong words

[zzcr]

修改文档错误单词

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Bug Fixes

  • Corrected a naming error for the button component, ensuring it displays and functions properly within the editing interface.
  • Simplified component registration by removing incorrect aliases, aligning template usage with registered components.

• Tests

  • Reduced complexity in test cases by removing unnecessary steps and interactions, streamlining the testing process.

[coderabbitai]

Walkthrough

This pull request fixes a typo in two Vue component files. The error involved an incorrect component name (tiny-butotn), which has been corrected to tiny-button in both the template and script sections. The import statement and component registration are updated accordingly. The underlying functionality of the components remains unchanged.

Changes

File	Change Summary
examples/.../edit/status-of-editing-composition-api.vue examples/.../edit/status-of-editing.vue	Corrected the typo in the component name from <tiny-butotn> to <tiny-button> in the template and script sections, and updated the import/component registration to use TinyButton correctly.
examples/.../slot/editor-slot.spec.js	Removed a sequence of steps in a test case for editor slot functionality, simplifying the test without altering public entity declarations.

Possibly related PRs

• style(action-menu): misspelled word #2431: Involves correcting typos in component names, specifically related to the naming of components and variables.
• fix(docs): fix components number #1754: Addresses the same component name correction from <tiny-butotn> to <tiny-button>.
• docs: fix plus doc load error #3016: Involves correcting a typo in the component name and its import statement, similar to the changes in this PR.

Suggested labels

documentation

Suggested reviewers

• gimmyhehe

Poem

I'm a rabbit, hopping with glee,
Fixing typos from A to Z.
From <tiny-butotn> to <tiny-button> I did mend,
Ensuring every click will transcend.
Code now hops smooth, on paths that extend! 🐇

---

📜 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 6681622 and f408239.

📒 Files selected for processing (1)

• examples/sites/demos/pc/app/grid/slot/editor-slot.spec.js (0 hunks)

💤 Files with no reviewable changes (1)

• examples/sites/demos/pc/app/grid/slot/editor-slot.spec.js

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: PR E2E Test (pnpm test:e2e3)

---

🪧 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.
• @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.

[petercat-assistant]

Walkthrough

This pull request addresses typographical errors in the Vue component files related to grid editing. Specifically, it corrects the spelling of the component name tiny-butotn to tiny-button in two Vue files, ensuring proper functionality and consistency in component usage.

Changes

File	Summary
examples/sites/demos/pc/app/grid/edit/status-of-editing-composition-api.vue examples/sites/demos/pc/app/grid/edit/status-of-editing.vue	Corrected the spelling of tiny-butotn to tiny-button and updated import statements accordingly.