Technical Writing Style Guide Language Collocations
Practise the standard verbs for keeping technical writing consistent.
0 / 5 completed
1 / 5
Fill in: 'We ___ the team's style guide for every piece of external documentation, so a reader moving between two different docs doesn't hit two different voices.'
We 'follow a guide' — the standard, simple collocation for adhering to an established writing standard. The other options are less idiomatic here.
2 / 5
Fill in: 'Letting every author pick their own terms for the same concept instead of following the guide can ___ a single feature described three different ways across the docs.'
We say inconsistent writing will 'leave' one feature described inconsistently — the standard, natural collocation for the resulting confusion. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ terminology across all documentation to one agreed term per concept, so 'sign in' and 'log in' don't quietly coexist and confuse a reader searching the docs.'
We 'standardize terminology' — the standard, simple collocation for enforcing consistent word choice across documents. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the guide itself to every new draft before publishing, using it as an actual checklist rather than a document nobody consults after the first week.'
We 'apply a guide' — the standard, simple collocation for actively using a style standard while writing. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the guide itself periodically as the product's language evolves, since a rule about an old feature name becomes actively wrong once that name changes.'
We 'update a guide' — the standard, simple collocation for keeping a writing standard current. The other options aren't idiomatic here.