Master the collocations for writing, reviewing, updating, and deprecating technical documentation.
0 / 5 completed
1 / 5
The tech writer's primary task for the quarter was to ___ documentation for all public-facing APIs.
Write documentation is the natural collocation for producing technical content for software products. 'Create along' and 'produce around' are informal. 'Draft out' is redundant — though 'draft documentation' is also correct.
2 / 5
A subject matter expert was asked to ___ accuracy of the deployment guide before it was published.
Review accuracy is the standard documentation and technical writing collocation for verifying that content is correct and up to date. 'Check along' and 'verify around' are informal. 'Confirm out' is not a standard phrase.
3 / 5
After the v3 API was released, the team needed to ___ docs to reflect the new authentication flow.
Update docs (or 'update documentation') is the standard collocation for modifying documentation to reflect changes in a product. 'Change along' and 'revise around' are informal. 'Fix out' does not convey the content update process.
4 / 5
When an older feature was removed from the product, the team had to ___ pages that were no longer relevant.
Deprecate pages is the standard documentation lifecycle collocation for marking content as outdated before removal. 'Remove along' and 'delete around' skip the deprecation step. 'Retire out' is not standard in a documentation context.
5 / 5
The team adopted Docs-as-Code to ensure that every code change would trigger a review to ___ documentation alongside the software.
Maintain documentation is the standard technical writing collocation for continuously keeping documentation current, accurate, and relevant. 'Keep along' and 'manage around' are informal. 'Preserve out' implies static conservation rather than active maintenance.