docs(auto-imports): capitalize title

[iiio2]

Since these are titles, I think it should be capitalized. Because other titles are also capitalized. For keeping consistency we can capitalize the titles.

Summary by CodeRabbit

• Documentation
  • Improved clarity and organization of the auto-imports guide for Nuxt.
  • Enhanced explanations on using composables and their lifecycle context.
  • Added guidance on disabling auto-imports and clarified explicit imports using #imports.
  • Included warnings about auto-imported ref and computed in templates.
  • Expanded structure with tips and links for better usability.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[coderabbitai]

Walkthrough

The documentation for auto-imports in Nuxt has been revised to enhance clarity and organization. Key changes include capitalizing section headers for consistency, refining content to highlight auto-importing capabilities, and clarifying the usage context for composables. Additional notes on disabling auto-imports, examples of code scenarios, and expanded explanations on explicit imports using the #imports alias have been added. A warning about the behavior of auto-imported ref and computed in templates is now included, along with improved structure featuring tips and links to related documentation.

Changes

File Path	Change Summary
docs/2.guide/1.concepts/1.auto-imports.md	Capitalized section headers, refined content on auto-importing, clarified composable usage context, added notes on disabling auto-imports, included examples of code scenarios, expanded explicit import section, added warning about ref and computed behavior, and improved overall structure with tips and links.

Poem

In the land of Nuxt, where imports play,
Clarity shines bright, guiding the way.
With headers so bold, and tips to share,
Composables dance, with nary a care.
A rabbit hops forth, with joy in its heart,
Celebrating changes, a fine work of art! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7f12ed4 and 6eda5a8.

📒 Files selected for processing (1)

• docs/2.guide/1.concepts/1.auto-imports.md (2 hunks)

🔇 Additional comments (2)

docs/2.guide/1.concepts/1.auto-imports.md (2)

51-51: LGTM! Title capitalization is now consistent.

The capitalization of "Vue and Nuxt Composables" follows proper title case and maintains consistency with other section headers.

---

162-162: LGTM! Title capitalization is now consistent.

The capitalization of "Auto-import from Third-Party Packages" follows proper title case and maintains consistency with other section headers.

---

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

[iiio2]

Thanks @danielroe , @manniL .