Skip to content

docs: fix typos, add useful information and examples #3376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 22, 2025

Conversation

oneminch
Copy link
Contributor

docs: fix typo

docs: add section on automatic setup via create-nuxt cli

docs: add an example usage section for hooks

docs: fix typo

πŸ”— Linked issue

N/A

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Changes in this PR introduce small improvements to the Nuxt Content docs. They don't close any issues or discussions.

  • I have added an example usage section to the 'Hooks' page.
  • I have also added an automatic setup (using create-nuxt) section to the 'Installation' page.
  • I fixed a couple of typos I noticed.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

docs: fix typo

docs: add section on automatic setup via create-nuxt cli

docs: add an example usage section for hooks

docs: fix typo
Copy link

pkg-pr-new bot commented May 22, 2025

npm i https://pkg.pr.new/@nuxt/content@3376

commit: 8949217

Copy link
Member

@farnabaz farnabaz left a comment

Choose a reason for hiding this comment

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

LGTM πŸ‘
Thanks

@farnabaz farnabaz merged commit 9c5b441 into nuxt:main May 22, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants