@PeterJones
Ok apols for late reply to your original request on how the warning could be rewritten.
Some background - I used to work as a field sales tech consultant for a tier 1 global data storage manufacturer and so was well versed in getting beaten up on engagements, nearly always for things that I wasn’t directly responsible for, but hey you’re there and folks want to unload, and often with justification. We often ended up rewriting all sorts of customer docs, but also shipped cases of European beer for the devs.
It’s especially hard if you’re involved with data security or content creation, since any issues impact productivity in terms of wasted time and worst of all, potential loss of content or even the fear of the latter.
Other than the golden rule of Don’t Break Stuff, (and if you must then prepare everyone by explaining the heck out of it) the general themes were to consider your audience and the impact for all of them e.g.
Who – are the affected users
What – is the change
Why – is the change req’d
When - is the impact
Where - can you go for more info and on how to roll-back.
I’m sure folks will say this is all overkill, and it would be for a crappy new app that didn’t create content, but that isn’t the case here, and so there are expectations! 😉 Ok time to stop rambling.
On this particular change, I fell at the first fence i.e. I had no idea whether I was affected. Only a fool would conclude that they would not be affected if they didn’t understand the warning!
Now I see your reply is updated, so thanks for considering the issue! :-)