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: apply sentence style capitalization to headings #3186

Closed

Conversation

devin-ai-integration[bot]
Copy link
Contributor

Apply sentence style capitalization to headings

This PR updates headings in extension documentation files to use sentence style capitalization, as requested in PR #3176.

Changes made:

  • Updated headings in pgcrypto.md
  • Updated headings in unaccent.md
  • Updated headings in uuid-ossp.md

Examples of changes:

  • "Performance and Indexing Considerations" → "Performance and indexing considerations"
  • "UUID Functions" → "UUID functions"

Technical terms like PostgreSQL commands, SQL keywords, and extension names remain capitalized.

Original PR: #3176
Requested by: Daniel Price ([email protected])
Link to Devin run: https://app.devin.ai/sessions/2c673d4636cb48ac81510fdbe33b6218

Copy link

vercel bot commented Mar 18, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
neon-next ❌ Failed (Inspect) Mar 18, 2025 7:03pm

Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add "(aside)" to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@danieltprice
Copy link
Collaborator

handled in another PR

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