WordPress.org
Get WordPress

Make WordPress Core

Opened 7 years ago

Closed 7 years ago

#36835 closed defect (bug) (fixed)

"backwards compatibility" vs. "backward compatibility"

Reported by: ocean90's profile ocean90 Owned by: drewapicture's profile DrewAPicture
Milestone: 4.6 Priority: normal
Severity: normal Version:
Component: General Keywords: has-patch commit
Focuses: docs Cc:

Description

I'm proposing to standardize on "backward compatibility" which seems to be the proper American spelling.

Attachments (3)

36835.patch​ (29.2 KB) - added by ocean90 7 years ago.
36835.2.patch​ (35.2 KB) - added by DrewAPicture 7 years ago.
Moar
36835.3.patch​ (1.9 KB) - added by ocean90 7 years ago.

Download all attachments as: .zip

Change History (5)

@ocean90
7 years ago

#1 @DrewAPicture
7 years ago

  • Keywords commit added

Jolly good. I concur.

@DrewAPicture
7 years ago

Moar

#2 @DrewAPicture
7 years ago

  • Owner set to DrewAPicture
  • Resolution set to fixed
  • Status changed from new to closed

In 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.

@ocean90
7 years ago

Note: See TracTickets for help on using tickets.