Fix multiple trivial spelling errors

[ottok]

Hello!

I've fixed multiple minor spelling errors under wp-includes (excluding 3rd party code from TinyMCE, JQuery, ID3).

The patches are rebased on the WordPress development trunk of today.

Most changes are in code comments but there is a few in internal function names too (not API changes of course).

For easier application, I've split these into 3 separate patches (attached).

After the changes I've ran phpunit and qunit so assure there are no regressions. Links to my public Travis-CI branches are also below. If you like git, all of these changes can be imported from my git repo as 3 separate commits.

​https://travis-ci.org/ottok/WordPress-develop/builds/170454678
​https://travis-ci.org/ottok/WordPress-develop/builds/170454582
​https://travis-ci.org/ottok/WordPress-develop/builds/170454549

[netweb]

Hi @ottok, thanks, here are some notes :)

The following are also external libraries so they shouldn't be patched by WordPress:

• tests/qunit/vendor/sinon.js and tests/qunit/vendor/qunit.js in fix-spelling-qunit.patch​

• tests/phpunit/data/formatting/sizzle.js, tests/phpunit/data/formatting/xssAttacks.xml in fix-spelling-phpunit.patch​

• src/wp-includes/js/colorpicker.js in fix-spelling-wp-includes.patch​

The following spelling changes are not required as the original spelling is correct:

• sandwich is the correct spelling so the tests/phpunit/data/formatting/whole-posts.php change in fix-spelling-phpunit.patch​ is not required.

• matching is the correct spelling so the tests/phpunit/includes/utils.php, tests/phpunit/tests/cache.php, and tests/phpunit/tests/cron.php changes in fix-spelling-phpunit.patch​ are not required.

[ottok]

Thanks @netweb for checking. I've attached patches that are updated as per above.

[netweb]

@ ottok, thanks, though could you please rename each of the patches so they end in .patch rather than .patch.2. By doing so it makes them a little a more readable here on Trac :)

[ottok]

@netweb done. I also switched filename to .diff as pros did so in #32257.

Personally I don't know how you can be effective (or in a project of this size even survive) with svn when there are no distributed branches, no effective diff tools across branches, branches cannot be squashed or rebased on latest master etc, but that is another story :)

[ocean90]

The patches still includes a few external libraries: wp-includes/class-pop3.php, wp-includes/js/imgareaselect/jquery.imgareaselect.js, wp-includes/pomo/translations.php, wp-includes/rss.php, tests/qunit/editor/tinymce/*.

Oh, and doing it all in one patch is fine, there's no need to split them up.

[SergeyBiryukov]

Replying to ocean90:

The patches still includes a few external libraries: wp-includes/class-pop3.php, wp-includes/js/imgareaselect/jquery.imgareaselect.js, wp-includes/pomo/translations.php, wp-includes/rss.php, tests/qunit/editor/tinymce/*.

Three of those appear to be treated as "adopted" rather than external, see the revision logs:

• https://core.trac.wordpress.org/log/trunk/src/wp-includes/class-pop3.php
• https://core.trac.wordpress.org/log/trunk/src/wp-includes/rss.php
• https://core.trac.wordpress.org/log/trunk/src/wp-includes/pomo/translations.php

I think it's fine to patch them.

[ottok]

I don't plan to produce more versions of the patches. You can easily omit the parts you don't want to apply as you are going to apply the patches manually anyway (this is svn and not a git merge request).

Thanks!

[ottok]

Can you please merge this? The more time passes, the more likely it is that the patches will not apply cleanly anymore on trunk.

This are trivial spelling fixes and already proof-read, so there shouldn't be anything stopping you from applying them all or partially.

[DrewAPicture]

In 39051:

Docs: Fix multiple trivial typos throughout a variety of core files.

Props ottok.
Fixes #38489.