IntenseWebs/WordPress
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

Browse Source 
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.

Built from https://develop.svn.wordpress.org/trunk@37431


git-svn-id: http://core.svn.wordpress.org/trunk@37397 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
Drew Jaynes
2016-05-13 18:41:31 +00:00
parent 1e40ba291e
commit b1804afeaf
51 changed files with 95 additions and 96 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
wp-includes/rest-api/class-wp-rest-response.php
View File

@@ -293,7 +293,7 @@ class WP_REST_Response extends WP_HTTP_Response {
*
* 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
*