Semantic versioning.
Most of the time. I use calendar versioning (calver) for my internal application releases because I work in IT. When the release happens is more consequential than breaking changes. And because it's IT, changes that break something somewhere are incredibly frequent, so we would constantly be releasing "major" versions that aren't really major versions at all.
OpenDocument.
Agreed compared to .doc and .docx. And if you're going to version control it, markdown instead of a binary blob.
For academic documents in STEM fields, I'd love to see a transition from LaTeX to Typst. Much cleaner, better error handling, and it has a web UI if people don't want to install a massive runtime on their own computer.
Not if they're going to disturb the relaxing cat.