Styles: More descriptive text for revisions timeline

[sacerro]

What?

Fixes #55648. Made in WordCamp Madrid 2023

Why?

Current text needs more context. Proposed text fits better.

How?

Replaced old text by new one proposed.

Testing Instructions

1. Open Theme Editor
2. Go to "Styles"
3. Change anything (a change is needed to display changes timeline)
4. Open revisions
5. Check if the new text appears.

Testing Instructions for Keyboard

N/A

Screenshots or screencast

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @sacerro! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[ramonjd]

Thanks for the PR!

The three clauses make it a bit of a mouthful in my opinion.

If we're seeking both clarity and guidance as mentioned in the issue, maybe we could:

1. describe what the user is looking at (the clarity)
2. provide instruction on how to restore styles (the guidance).

Not being prescriptive, these are just ideas. Language is fuzzy 😄

E.g.,

This is pretty verbose:

Click on previously saved styles to preview them. To restore a selected version to the editor, hit "Apply". When you're ready, save the template to commit your changes.

A bit more condensed:

A timeline of saved changes to your site's styles. Click "Apply" to restore a selected version in the editor.

What do you reckon?

As a heads up, the revisions panel will be getting a UX makeover soon: #55776

[sacerro]

I think the verbose option is the best. It explains better to the user what this panel do.
What do you think @pablohoneyhoney?

[sacerro]

I replace the text by the one you suggested 💪

[provenself]

@sacerro wording looks good on the longer option, but the period needs to go inside the quotation mark like so:

Click on previously saved styles to preview them. To restore a selected version to the editor, hit "Apply." When you're ready, save the template to commit your changes.

[ramonjd]

Thanks @provenself

I've updated the copy to reflect the latest changes.

I'll merge this PR.

Thanks also to @sacerro !

[ramonjd]

Sorry, I'd set this to auto merge, but I think forgot to approve 🤦🏻

Thanks for your patience!

[ramonjd]

👍🏻

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: [Type] Enhancement, [Type] Copy, Needs Copy Review, First-time Contributor, Global Styles.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.