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/load.php

    r37342 r37431  
    332332            define( 'WP_LANG_DIR', WP_CONTENT_DIR . '/languages' );
    333333            if ( !defined( 'LANGDIR' ) ) {
    334                 // Old static relative path maintained for limited backwards compatibility - won't work in some cases
     334                // Old static relative path maintained for limited backward compatibility - won't work in some cases.
    335335                define( 'LANGDIR', 'wp-content/languages' );
    336336            }
     
    345345            define( 'WP_LANG_DIR', ABSPATH . WPINC . '/languages' );
    346346            if ( !defined( 'LANGDIR' ) ) {
    347                 // Old relative path maintained for backwards compatibility
     347                // Old relative path maintained for backward compatibility.
    348348                define( 'LANGDIR', WPINC . '/languages' );
    349349            }
Note: See TracChangeset for help on using the changeset viewer.