docs: Grammar overhaul getting started

[GalacticHypernova]

🔗 Linked issue

The splitting of #20636 into smaller chunks

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 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)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Smaller chunk of the overhaul for easier reviewing and implementation

📝 Checklist

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

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
Nuxt Docs	Edit on Studio ↗︎	View Live Preview	cfd568e

[GalacticHypernova]

@danielroe @DamianGlowala Hope this is small enough! If not please do let me know and I'll release it in batches of 2-3 files at a time. Also sorry for my absence with this PR, was caught up with life.

[danielroe]

I think we should close this PR as it is out of sync with the current docs.

A more general note: it's a mix of really good wording changes and ones that don't quite strike the right tone for me. Anything too extreme (like 'exquisite') I would avoid, as would changes that are largely equivalent to current values (like changing 'without learning TypeScript' to 'without having to learn TypeScript'). I'm aware this is very subjective.

Having said that, I would love to see this reopened as PRs targeting individual sections of the docs for easier (and faster 🙈) review.