Spell-checking forces text of user issues to be changed in the release notes/

I'd say this is fairly minor and depends on the policy of each project regarding spelling of the text in user issues.

My own policy in the engine project (and the whole project when I was responsible for it) was always to keep the exact text entered by the user unless it wasn't understandable at all. (In that case I'd change it and add a comment to the issue) I felt (and still do) that it was disrespectful to "correct" trivial errors made by the user...

The user descriptions live in the GitHub issues database. When creating releases, they are copied verbatim to the Release Notes on GitHub by an automatic process. Creating release notes on the website is currently a manual process, which I do using cut and paste from GitHub. In future, I would have wanted to automate it.

Whether done manually or not, however, the issue descriptions, which are listed in two places in GitHub are sometimes invalid for the release notes on the website and must be changed. This bothers me a bit because the description of a given issue is now in three places and one of them is different. I'd suggest eliminating spell checking on the release notes if that's easy to do.

Start with the release-note process described in this issue, including the GitHub release notes and the website's manual copy-and-paste step. Determine where spell-checking changes issue text and whether that process can preserve the original wording; done means release notes no longer require altering copied issue descriptions.