Copy: improve overrides modal for enabling and disabling

[annezazu]

For enabling and disabling overrides, I found the copy to be a bit stiff and hard to understand. Let's try to iterate (if we can).

Enabling:

Overrides are changes you make to a block within a synced pattern instance. Use overrides to customize a synced pattern instance to suit its new context. Name this block to specify an override.

Disabling:

Are you sure you want to disable overrides? Disabling overrides will revert all applied overrides for this block throughout instances of this pattern.

[annezazu]

Some riffing:

Overrides are changes you make to a block within a synced pattern instance. Use overrides to customize a synced pattern instance to suit its new context. Name this block to specify an override.

Adding an override will allow this block to be edited within any instance of this synced pattern. To set an override, name this block.

Are you sure you want to disable overrides? Disabling overrides will revert all applied overrides for this block throughout instances of this pattern.

Are you sure you want to disable an override for this block? By disabling, any customized content for this block throughout every instance of this pattern will be reverted to the original synced pattern.

[provenself]

These are looking good! Defer to you on the actual functionality, but these feel a little different:

within a synced pattern instance

and

within any instance of this synced pattern

That is, I read the original as overriding turning a chosen instance into its own new pattern; I read the revision as overriding across the pattern ("any" functioning as "every"). (Secondarily, I'm not clear how this differs from "detach" in the current version.) To that tend, suggesting a tiny tweak:

Adding an override will allow this block to be edited within any instance of this synced pattern. To set an override, name this block.

Adding an override will make this block editable within a chosen instance of the synced pattern. To set an override, name this block.

Are you sure you want to disable an override for this block? By disabling, any customized content for this block throughout every instance of this pattern will be reverted to the original synced pattern.

Are you sure you want to disable an override for this block? Any customized content for this block throughout every instance of this pattern will be reverted to the original synced pattern.

[marybaum]

I think I would make this singular (and how much experience does the person who sees this have with synced patterns?) If a relatively new person, maybe something like this:

An override is a change you make to a block inside a particular instance of a synced pattern. Generally, you'll do that to make the pattern more specific to what you're doing. Name the block with the override, and you'll have saved it to edit later in any instance of that synced pattern.

The second sentence is optional, I think, but tells a new user why they might want to do the override.

To disable:

Are you sure you want to disable this override? If you do, any custom content in this block, across every instance of this pattern, will disappear, and the content of the original synced pattern will replace it.

More jarring, but clearer in the implications.

[annezazu]

Thank you both for helping here! Merging suggestions from you both and landing here to keep it concise yet clear:

Enabling an override

Adding an override will allow this block to be edited within any instance of this synced pattern. To set an override, name this block.

Disabling an override

Are you sure you want to disable an override for this block? By disabling, any custom content for this block throughout every instance of this pattern will be reverted to the original content of the synced pattern.

Going to have this as a needs dev task :)

[shreya0204]

Hi @annezazu

I've made some changes to the modal message in Gutenberg to better explain the override settings. Could you please review them at your convenience?

[talldan]

The changes look good to me. I think @richtabor worked on the copy originally, so might be good to loop in on the changes.

[talldan]

Removing this from the 6.6 board given the string freeze is coming up and there's still discussion on the PR about the right copy - #61948.