These more readable notes are a lot better @tomspilman

I think generally the changelog isn't great because commit messages or PR titles tend to be more developer-oriented while the changelog is for people using MonoGame and should not be about implementation. For example a change I did had the message

Use short for parameter count in effect binary.

while the actual problem this fixed was #5995, so I changed the message to

Support arrays > 255 elements in shaders.

in SickheadGames#19. That conveys what's actually interesting to MG users. Things that are not interesting for MG users should not be in the changelog IMO (except big stuff like the Protobuild migration).
I also don't think documentation changes should go in the changelog. There's also a bunch of entries that relate to fixes after migrating to the SDK project system and to .NET Core which are not useful for users to read through and which would never have had a changelog entry if we manually kept it.

I don't think we should spend hours going through these entries though. This will be better from now on with a manual changelog.

@Jjagg @harry-cpp in the future on doc PRs like this we should always "squash and merge". Don't think it is useful to have a dozen random doc edit commits in the history.