Fix typo: “such as; Performance” → “such as performance”

[aarti1318]

This fixes a typo on the site health page on recommended improvement section

[aarti1318]

This patch fixes a minor typo on the site health screen. Let me know if any changes are needed. Thanks!

[rollybueno]

Nice catch. We don't need needs-refresh tag. This tag is for refreshing dormant patch, usually months or years old with no movement, and no need for testing.

Fix: Typo error “such as; Performance” → “such as performance” - see #63787

Trac ticket: https://core.trac.wordpress.org/ticket/63787

[sabernhardt]

[53950] added the message.

I would also like to split the description into two sentences:

Recommended items are considered beneficial to your site, although not as important to prioritize as a critical issue. They may include improvements to things such as performance, user experience, and more.

[aarti1318]

Thank you for the feedback!

Updated patch to include the revised description suggested by @sabernhardt, in addition to the original typo fix.

Attached latest patch file - 63787-typo-fix.patch

[westonruter]

I think the last sentence can be further simplified:

They may include improvements to things such as performance and user experience.

The "such as" makes the "and more" redundant.

But since things come better in threes, how about adding "security" since this is one of the common categories:

They may include improvements to things such as security, performance, and user experience.

[aarti1318]

That's a good suggestion to include security.
What if we replace 'things' with 'areas'?
"They may include improvements in areas such as security, performance, and user experience."

[westonruter]

Good idea, "areas" does sound better than "things".

[aarti1318]

Added patch to change ‘things’ to ‘areas’ as discussed.

[westonruter]

In 60609:

Site Health: Improve descriptions for critical issues and recommended improvements.

Props aarti1318, naveendwivedi, westonruter, sabernhardt, dhruvang21, rollybueno.
Fixes #63787.

[westonruter]

In looking at the description for critical issues, I found it was missing an apostrophe in "sites". I also broke up the compound sentence into two sentences, as was done for the recommended improvements description.

@aarti1318 Thank you for opening the ticket and for your first contribution.

A couple tips: When uploading patches to Trac, it's best if each successive patch contains the entire set of changes being proposed for commit. Otherwise, applying the patches requires multiple calls to apply the patch files. But even better is to open a pull request on GitHub with the changes, as @naveendwivedi did in <​https://github.com/WordPress/wordpress-develop/pull/9385>. This not only avoids the headache of attaching patch files to Trac, but it also runs all the automated tests to ensure that coding standards are adhered to and that tests still pass.

Thanks again!