Changeset 37431 for trunk/src/wp-includes/rest-api/class-wp-rest-response.php

Timestamp:

05/13/2016 06:40:19 PM (8 years ago)

Author:

DrewAPicture

Message:

Docs: Standardize on 'backward compatibility/compatible' nomenclature in core inline docs.

Also use 'back-compat' in some inline comments where backward compatibility is the subject and shorthand feels more natural.

Note: 'backwards compatibility/compatibile' can also be considered correct, though it's primary seen in regular use in British English.

Props ocean90.
Fixes #36835.

File:

• trunk/src/wp-includes/rest-api/class-wp-rest-response.php (modified) (1 diff)

trunk/src/wp-includes/rest-api/class-wp-rest-response.php

@@ -294 +294 @@
          * Well-behaved clients should expand and normalise these back to their
          * full URI relation, however some naive clients may not resolve these
-         * correctly, so adding new CURIEs may break backwards compatibility.
+         * correctly, so adding new CURIEs may break backward compatibility.
          *
          * @since 4.5.0