Skip to content
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

docs: fix typo #1634

Merged
merged 5 commits into from
Oct 24, 2022
Merged

docs: fix typo #1634

merged 5 commits into from
Oct 24, 2022

Conversation

selemondev
Copy link
Contributor

πŸ”— Linked issue

❓ 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

πŸ“ Checklist

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

@netlify
Copy link

netlify bot commented Oct 23, 2022

βœ… Deploy Preview for nuxt-content ready!

Built without sensitive environment variables

Name Link
πŸ”¨ Latest commit 6c21fed
πŸ” Latest deploy log https://app.netlify.com/sites/nuxt-content/deploys/63553bd9c6db690009ef4d88
😎 Deploy Preview https://deploy-preview-1634--nuxt-content.netlify.app
πŸ“± Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@gitguardian
Copy link

gitguardian bot commented Oct 23, 2022

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

πŸ”Ž Detected hardcoded secret in your pull request
GitGuardian id Secret Commit Filename
- Algolia Keys d0a58d3 docs/nuxt.config.ts View secret
πŸ›  Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


πŸ¦‰ GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

docs/content/3.guide/1.writing/7.document-driven.md Outdated Show resolved Hide resolved
docs/content/3.guide/3.recipes/1.sitemap.md Outdated Show resolved Hide resolved
selemondev and others added 2 commits October 23, 2022 06:03
Co-authored-by: nobkd <44443899+nobkd@users.noreply.github.com>
Co-authored-by: nobkd <44443899+nobkd@users.noreply.github.com>
@atinux atinux changed the title Docs/fix typo docs: fix typo Oct 24, 2022
@atinux atinux merged commit 516838b into nuxt:main Oct 24, 2022
@selemondev selemondev deleted the docs/fix-typo branch October 25, 2022 03:20
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.

3 participants