@Torinde , I'm just skimming through the changes you made here, and wow: so many fixes and clarifications, plus the addition of the 32bit build w/ hash. This is great!

@Torinde, if you check your email, you've been added to the DOSBox Staging team (I think you have to accept it).

Welcome! You have write access now, which means you can administer tickets, projects, and PR attributes (labels, assignments, close/open, etc).

More importantly, you can now create your own branches directly inside the repository (instead of needing to fork the repo).

We create our branches named like this: "initials/branch-name-revision"

You can see here, I named this branch torinde/docs-os-support-1 (as I don't know your initials). When the branch passes review, maintainers will merge its commits into main followed by deleting the branch.

We have some notes here on how we work with PRs and branches. Although these mention "code", feel free to mentally substitute that with "documentation", as both go through the same process (even compilation in a sense.. MkDocs renders the markdown to HTML, with the website being the interactive result).

https://github.com/dosbox-staging/dosbox-staging/wiki/Maintenance-and-Release-Notes#3-contributing-and-reviewing-prs

Also, @FeralChild64 and @johnnovak both offered very helpful comments to another recent contributor here (which I highly recommend):

#2248 (comment)