Improve clarity of Layout Builder "Revert changes" confirmation form

@mark_fullmer, thanks for the idea and the MR.

In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Also mentioned on the version → section of the list of issue fields documentation.

Good idea! Put in a suggestion.

I think we should look at RevertOverridesForm too, that might be even more confusing than this one

Would it be appropriate to change the target branch of the existing merge request to 11.x (the default branch), or would you recommend creating a new branch from 11.x and applying the suggested changes there because I don't see any option to change the target branch?

Please advise on the preferred approach to proceed in line with current contribution practices.

In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed

I've changed the target branch from 11.2.x to 11.x. Thanks!

I think we should look at RevertOverridesForm too, that might be even more confusing than this one

Agreed, although I'm not sure it's feasible to create a generic statement that accurately reflects what that action will do, given its variability based on site configuration. On one site, this might mean that the entity's Layout Builder sections will be reverted to a single, emtpy, one-column section. On others, "Revert layout" could restore the default sidebar content and order of the main content.

Given this, I think that issue should be dealt with separately.

Opened 📌 Improve clarity of Layout Builder "Revert to defaults" confirmation form Active for the revert form. Agree we should handle it seperately.

This is RTBC from me. I think its much better.