What the style guides say
“manpower”
5 of 16 open style guides have a rule about “manpower.” They don’t agree on what to write instead: 3 say “personnel,” and the rest give other answers.
What to write instead, by guide
- personnel 3 guides
Google, Grafana, Elastic
- workforce 1 guide
Microsoft
- GitLab team members 1 guide
GitLab
Guide by guide
- Google Write personnel Gender bias · error
- Microsoft Write workforce Gender bias · error
- GitLab Write GitLab team members Inclusive language · warning
- Grafana Write personnel Google gender bias · error
- Elastic Write personnel Gender bias · suggestion
No rule names it in Red Hat, IBM, Datadog, Splunk, Salesforce, Docker, Canonical, Apify, Spectro Cloud, 18F, GOV.UK. That doesn’t mean those guides approve of it, only that no rule lists it.
Catch it in every draft
Each line above is a rule one of these organizations publishes for Vale, an open-source linter for prose. Install a guide’s rules and Vale flags the term wherever it appears, in your editor and on every pull request.