word-001 should GuidesAPI docsMarketingBlog Use one term consistently to represent one concept across all documentation.
Word choice
This page holds the core terminology rule; verdicts on specific terms live in the word list.
One term per concept
Section titled “One term per concept”Examples
- ✓ Select a region. After you select a region, the zone list updates.
- ✗ Select a region. After you choose a region, the zone list updates.
Rationale
Switching terms for the same concept makes a reader wonder whether they are the same thing; one term keeps it unambiguous and translatable.
Use ‘and’, not ‘as well as’
Section titled “Use ‘and’, not ‘as well as’”word-002 should GuidesAPI docsMarketingBlog Join items with ‘and’ rather than ‘as well as’; ‘as well as’ adds length without adding meaning and can obscure whether the items carry equal weight.
Examples
- ✓ The SDK supports Python and Go.
- ✗ The SDK supports Python as well as Go.
Rationale
‘And’ states the conjunction plainly; ‘as well as’ is wordier and signals that the second item is secondary, which is usually not the intent in a list of supported things.