WordPress ruleset: fix deprecation notices coming through
WordPress ruleset: fix deprecation notices coming through

This "hack" works and seems to be the simplest solution to the issue at hand.

**Beware**: just like in the original VIP deprecation, the VIP sniffs are being `exclude`d. This means that if people use the `WordPress` ruleset and in their custom ruleset reference any of the VIP sniffs, they will **not** see the deprecation warning.

Note: This uses `<exclude>` rather than `severity` as in PHPCS 2.9 severity could only be changed on error code level.
Custom rulesets can overrule this  by changing the `severity` of either the category if using PHPCS 3.x or of the error codes when using PHPCS 2.9.

Fixes 1425

Includes a few more spelling fixes in the same ruleset.

WordPress-Coding-Standards/WordPress-Coding-Standards,WordPress-Coding-Standards/WordPress-Coding-Standards,WordPress-Coding-Standards/WordPress-Coding-Standards,paulschreiber/WordPress-Coding-Standards,paulschreiber/WordPress-Coding-Standards,WordPress-Coding-Standards/WordPress-Coding-Standards,jrfnl/WordPress-Coding-Standards,jrfnl/WordPress-Coding-Standards,jrfnl/WordPress-Coding-Standards,paulschreiber/WordPress-Coding-Standards,paulschreiber/WordPress-Coding-Standards,jrfnl/WordPress-Coding-Standards