Changeset 37431 for trunk/src/wp-includes/class-wp-user-query.php

Timestamp:

05/13/2016 06:40:19 PM (10 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:

• trunk/src/wp-includes/class-wp-user-query.php (modified) (5 diffs)

trunk/src/wp-includes/class-wp-user-query.php

@@ -737 +737 @@
 
         /**
-         * Make private properties readable for backwards compatibility.
+         * Make private properties readable for backward compatibility.
          *
          * @since 4.0.0
@@ -752 +752 @@
 
         /**
-         * Make private properties settable for backwards compatibility.
+         * Make private properties settable for backward compatibility.
          *
          * @since 4.0.0
@@ -768 +768 @@
 
         /**
-         * Make private properties checkable for backwards compatibility.
+         * Make private properties checkable for backward compatibility.
          *
          * @since 4.0.0
@@ -783 +783 @@
 
         /**
-         * Make private properties un-settable for backwards compatibility.
+         * Make private properties un-settable for backward compatibility.
          *
          * @since 4.0.0
@@ -797 +797 @@
 
         /**
-         * Make private/protected methods readable for backwards compatibility.
+         * Make private/protected methods readable for backward compatibility.
          *
          * @since 4.0.0