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.


git-svn-id: https://develop.svn.wordpress.org/trunk@37431 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
Drew Jaynes
2016-05-13 18:40:19 +00:00
parent db0ecb6469
commit 195572596b
49 changed files with 93 additions and 94 deletions

View File

@@ -458,7 +458,7 @@ class WP_Text_Diff_Renderer_Table extends Text_Diff_Renderer {
}
/**
* Make private properties readable for backwards compatibility.
* Make private properties readable for backward compatibility.
*
* @since 4.0.0
* @access public
@@ -473,7 +473,7 @@ class WP_Text_Diff_Renderer_Table extends Text_Diff_Renderer {
}
/**
* Make private properties settable for backwards compatibility.
* Make private properties settable for backward compatibility.
*
* @since 4.0.0
* @access public
@@ -489,7 +489,7 @@ class WP_Text_Diff_Renderer_Table extends Text_Diff_Renderer {
}
/**
* Make private properties checkable for backwards compatibility.
* Make private properties checkable for backward compatibility.
*
* @since 4.0.0
* @access public
@@ -504,7 +504,7 @@ class WP_Text_Diff_Renderer_Table extends Text_Diff_Renderer {
}
/**
* Make private properties un-settable for backwards compatibility.
* Make private properties un-settable for backward compatibility.
*
* @since 4.0.0
* @access public