✏️ Report small docs improvements, including typos or broken links

[svlandeg]

Description

This thread should be used to report clear typos, broken links, or other small issues with the language used throughout the documentation.

Every once in a while, a maintainer will collect all these reports and will create a PR with all of them, to avoid having to review & merge many small PRs.

We will not be accepting any more user PRs to update typos, links or rephrasings of the documentation/tutorial.

[VectorPeak]

Thanks for helping keep the docs tidy. This discussion is the right place for small, clear documentation issues such as typos, broken links, duplicated words, outdated anchors, or wording that is obviously incorrect.

When reporting one, please include:

• The docs page URL
• The section heading, if relevant
• The current text or link
• The suggested replacement
• A short note if the problem is not obvious from the text alone

Please keep reports focused on small documentation fixes only. Larger tutorial changes, behavior questions, feature requests, or API design discussions should go in a separate issue or discussion so they can be handled properly.

As mentioned in the description, typo/link/rephrasing PRs are not being accepted individually anymore. Maintainers will periodically collect reports from this thread and batch them into a single PR to keep review overhead manageable.

Duplicate reports are okay, but checking the latest comments before posting helps avoid extra noise.

---

If my answer solved your problem, you can click answered the question. I'm really here to help, and along the way I'm also collecting Galaxy Brain badges haha 😆