[wp-trac] [WordPress Trac] #36835: "backwards compatibility" vs. "backward compatibility"
WordPress Trac
noreply at wordpress.org
Fri May 13 18:40:22 UTC 2016
#36835: "backwards compatibility" vs. "backward compatibility"
------------------------------+---------------------------
Reporter: ocean90 | Owner: DrewAPicture
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 4.6
Component: General | Version:
Severity: normal | Resolution: fixed
Keywords: has-patch commit | Focuses: docs
------------------------------+---------------------------
Changes (by DrewAPicture):
* owner: => DrewAPicture
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"37431"]:
{{{
#!CommitTicketReference repository="" revision="37431"
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.
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36835#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list