WordPress.org

Make WordPress Core


Ignore:
Timestamp:
05/13/2016 06:40:19 PM (5 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:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-includes/theme.php

    r37313 r37431  
    665665 *
    666666 * Accepts one argument: $stylesheet of the theme. It also accepts an additional function signature
    667  * of two arguments: $template then $stylesheet. This is for backwards compatibility.
     667 * of two arguments: $template then $stylesheet. This is for backward compatibility.
    668668 *
    669669 * @since 2.5.0
     
    16351635            // As stated above, the first value wins.
    16361636            // Once we get to wp_loaded (just-in-time), define any constants we haven't already.
    1637             // Constants are lame. Don't reference them. This is just for backwards compatibility.
     1637            // Constants are lame. Don't reference them. This is just for backward compatibility.
    16381638
    16391639            if ( defined( 'NO_HEADER_TEXT' ) )
Note: See TracChangeset for help on using the changeset viewer.