docs: remove invalid spaces

[coderwyd]

Description

Fixed interface display error.

Before:

After:

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• Documentation
  • Streamlined installation instructions in the English and Chinese README files for clarity.
  • Improved formatting and readability across various documentation files, including build, development, server, quick-start, and CLI guides by removing extraneous blank lines.
  • Corrected capitalization of "CSpell" in the code quality standards section.
  • Enhanced overall readability of documentation without impacting functionality.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 745c738

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The recent changes across various documentation files are primarily focused on minor formatting adjustments, including the removal of unnecessary blank lines and corrections to tool names. These enhancements aim to improve clarity and readability without impacting the functionality or logic of the instructions. Overall, the updates streamline the presentation of commands and information, making it easier for users to follow along.

Changes

Files	Change Summary
README.md, README.zh-CN.md	Removed blank lines to improve formatting of installation instructions.
docs/src/guide/essentials/*.md	Minor formatting adjustments, including removal of extraneous newlines in various sections.
docs/src/guide/introduction/*.md	Removed blank lines before code blocks to streamline installation and startup command presentation.
docs/src/guide/project/*.md	Eliminated unnecessary line breaks in documentation for commands related to changesets and CLI.
docs/src/guide/other/faq.md	Removed a single line of whitespace, purely cosmetic change.
docs/src/guide/introduction/vben.md	Corrected capitalization of "cspell" to "CSpell" for accuracy in tool names.

Poem

🐇 In the land of code so bright,
Blank lines vanish, what a sight!
Clarity blooms in every part,
Enhancing docs, a work of art.
With each tweak, our tools align,
Hooray for changes, oh so fine! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0c18912 and 745c738.

Files selected for processing (10)

• README.md (1 hunks)
• README.zh-CN.md (1 hunks)
• docs/src/guide/essentials/build.md (6 hunks)
• docs/src/guide/essentials/development.md (2 hunks)
• docs/src/guide/essentials/server.md (1 hunks)
• docs/src/guide/introduction/quick-start.md (2 hunks)
• docs/src/guide/introduction/vben.md (1 hunks)
• docs/src/guide/other/faq.md (1 hunks)
• docs/src/guide/project/changeset.md (1 hunks)
• docs/src/guide/project/cli.md (8 hunks)

Files skipped from review due to trivial changes (10)

• README.md
• README.zh-CN.md
• docs/src/guide/essentials/build.md
• docs/src/guide/essentials/development.md
• docs/src/guide/essentials/server.md
• docs/src/guide/introduction/quick-start.md
• docs/src/guide/introduction/vben.md
• docs/src/guide/other/faq.md
• docs/src/guide/project/changeset.md
• docs/src/guide/project/cli.md