I’ve tended to believe that the content of buttons should answer the question being asked — which is why the default buttons in most frameworks should never be used. In your #1, the “Bad” example answers the question being asked in both the title and the body text. It’s a coherent conversation.

I get what you’re saying there, but is there not cognitive dissonance, additional cognitive load, if the buttons do not follow the preceding content? Sure, users will often skip the intervening text, going directly from headline to button, especially if there is a lot of body text. But our UIs are conversations, and it seems to me that if we don’t make the conversation clear, confusion could ensue.

That said, this could be an argument for modifying the rest of the content in the dialog box. Maybe determine the best button content first, and then design good supporting content that keeps the conversation coherent.