Drew Jaynes b1804afeaf 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. Built from https://develop.svn.wordpress.org/trunk@37431 git-svn-id: http://core.svn.wordpress.org/trunk@37397 1a063a9b-81f0-0310-95a4-ce76da25c4cd		2016-05-13 18:41:31 +00:00
..
comments.php	Docs: Standardize on 'backward compatibility/compatible' nomenclature in core inline docs.	2016-05-13 18:41:31 +00:00
embed-404.php	Docs: Reference the correct embed templates and template parts filenames in headers for embed files introduced or changed in 4.5.	2016-03-28 18:24:27 +00:00
embed-content.php	Docs: Reference the correct embed templates and template parts filenames in headers for embed files introduced or changed in 4.5.	2016-03-28 18:24:27 +00:00
embed.php	Docs: Reference the correct embed templates and template parts filenames in headers for embed files introduced or changed in 4.5.	2016-03-28 18:24:27 +00:00
footer-embed.php	Docs: Standardize file headers for two embed templates introduced in [36693] for #34561.	2016-03-28 18:27:26 +00:00
footer.php	Docs: Standardize on 'backward compatibility/compatible' nomenclature in core inline docs.	2016-05-13 18:41:31 +00:00
header-embed.php	Docs: Standardize file headers for two embed templates introduced in [36693] for #34561.	2016-03-28 18:27:26 +00:00
header.php	Docs: Standardize on 'backward compatibility/compatible' nomenclature in core inline docs.	2016-05-13 18:41:31 +00:00
sidebar.php	Docs: Standardize on 'backward compatibility/compatible' nomenclature in core inline docs.	2016-05-13 18:41:31 +00:00