I find it helpful when writing apology posts to start it by writing down the timeline of events. Don’t insert any commentary attempting to justify anything in this part, it just comes off as defensive. Instead just outline what happened though you can include the immediate cause of decisions you made.
“Because I was worried about how people would react to X I decided to do Y”
Then after that you can write all the stuff that they list in this post.
I think it helps a lot to get the audience into the same situation you where in in their minds before understanding the context of how you actually screwed up.
There are lots of occasions where we made a change the players didn't like, or we screwed up in a way that led to economic damage to some players, or just had an operational issue that led to a bunch of downtime.
Incident reports such as this one are incredibly valuable for understanding what went wrong and deficiencies that need to be addressed, but also what went well (e.g. point-in-time rollback as effective mitigation).
The full timeline is valuable since you can look back on it and determine what went wrong when, so you can determine what changes need to happen to prevent these same issues in the future.
One thing I find is that incident reports such as these are most useful internally, but when communicated externally, they demonstrate that you're taking the underlying issues seriously and are committed to addressing them.
“Because I was worried about how people would react to X I decided to do Y”
Then after that you can write all the stuff that they list in this post.
I think it helps a lot to get the audience into the same situation you where in in their minds before understanding the context of how you actually screwed up.