I love the evolving proofreading feature. I am presently editing an arrangement that was “perfect in every way” or so I thought, but there were many mistakes in the first rehearsal.
The most common mistakes resulted from the fact that this chart has some rather dense (colorful) harmonization. And while the notes may have been technically correct – and fully correct in the eyes of a musicologist – in the real world, this led to double flats and sharps. That’ s bad enough , but the bigger problem was that adjacent notes ended up with different enharmonic spellings for the same pitch (and yes, i understand that with just intonation, each enharmonic may be a slightly different pitch, depending on its role in the harmony)
Be that as it may, a Gb followed by an F# is prone to be misread. And certainly, sequences like A# Cbb can make players downright angry, and they don’t want to hear that this may be technically correct.
So I would very much appreciate a proofreading rule identifying any double flats or double sharps. And a separate rule for adjacent notes of the same pitch but different enharmonic spelling. Musical purists can turn off these rules if they like.