docs: Issues identified while working at PyconDE Sprints

[AVHopp]

This issue is intended to be used by the participants of the "pixi documentation sprint" hosted before PyconDE 2026. The idea is that the participants can simply collect all of the minor issues and thoughts in one place such that we can coordinate the work on those. This approach was suggested by @travishathaway.

UPDATE: List of PR's that have been developed here (collected from the comments below and by manually going throu:

• docs: Fixed typos and capitals and added clarification for channels in Rust tutorial #5874
• docs: Some minor improvements to the python tutorial #5875
• docs: clarify scheduled CVE scanning and two threat models in security guide #5877
• docs: fix npm build example in pixi manifest #5879
• docs: Add "basic idea" overview to basic usage #5881
• docs: improve VS Code support documentation #5884
• docs: add how pixi works section with mermaid diagram #5887
• docs: Use canonical_version: latest in mike #5888
• docs(add): new examples for using channels with pixi add #5889
• docs: add guide for using pixi with lefthook, pre-commit, and prek (#… #5891
• updated docs (pixi add): document channel::package usage example #5893

[AVHopp]

PRs that have been create:

• docs: Fixed typos and capitals and added clarification for channels in Rust tutorial #5874 by @carecodeconnect for fixing typos and capitals and added clarification for channels in Rust tutorial
• docs: Some minor improvements to the python tutorial #5875 by @AVHopp for minor improvements on the python tutorial

[dk-moriha]

I have created!

• docs: clarify scheduled CVE scanning and two threat models in security guide #5877 by @dk-moriha for minor improvements on the Security tutorial

[dk-tanio]

It is a very small change, but the command looked incorrect, so I submitted a fix.

• docs: fix npm build example in pixi manifest #5879 by @dk-tanio for fixing a small command example in docs/reference/pixi_manifest.md

[AVHopp]

I opened another PR #5888 to fix #4635