Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adhere to WordPress core glossary #12579

Closed
swissspidy opened this issue Dec 4, 2018 · 1 comment
Closed

Adhere to WordPress core glossary #12579

swissspidy opened this issue Dec 4, 2018 · 1 comment
Labels
Good First Issue An issue that's suitable for someone looking to contribute for the first time [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Type] Developer Documentation Documentation for developers

Comments

@swissspidy
Copy link
Member

In a number of places, documentation uses the term "backwards compatibility" instead of "backward compatibility", which is the officially recommended spelling according to https://make.wordpress.org/core/handbook/glossary/ and https://make.wordpress.org/core/handbook/best-practices/spelling/

Situation is probably similar for other words too.
@swissspidy swissspidy added [Type] Developer Documentation Documentation for developers [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later labels Dec 4, 2018
@mtias mtias added the Good First Issue An issue that's suitable for someone looking to contribute for the first time label Dec 4, 2018
@HardeepAsrani
Copy link
Contributor

I'm wondering if the file names should also be changed, such as? https://github.com/WordPress/gutenberg/blob/master/docs/designers-developers/developers/backwards-compatibility/README.md And some are probably indexed by search engines.

@mkaz mkaz mentioned this issue Dec 10, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Good First Issue An issue that's suitable for someone looking to contribute for the first time [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Type] Developer Documentation Documentation for developers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mtias @swissspidy @HardeepAsrani