Master the collocations for communicating changes, highlighting features, documenting breaking changes, and crediting contributors.
0 / 5 completed
1 / 5
The release manager drafted a changelog to ___ changes clearly to users upgrading from the previous version.
Communicate changes is the standard release notes collocation for clearly conveying what has changed in a new software version to end users and developers. 'Explain along' and 'describe around' are informal. 'Detail out' is redundant.
2 / 5
The product team structured release notes to ___ features introduced in the latest version at the top of the document.
Highlight features is the standard release notes collocation for drawing attention to important new capabilities in a release. 'List along' and 'show around' are informal. 'Call out' is slightly informal but acceptable; 'highlight' is the most natural choice.
3 / 5
The API team added a prominent section to ___ breaking changes so that consumers could plan their upgrades.
Document breaking changes is the standard API and release notes collocation for formally recording incompatible modifications that require consumer action. 'List along' and 'note around' are informal. 'Flag out' is not a standard phrase.
4 / 5
The release notes included an acknowledgements section to ___ contributors who submitted bug fixes and improvements.
Credit contributors is the standard open-source and release notes collocation for recognising the people whose work is included in a release. 'Thank along' and 'mention around' are informal. 'Acknowledge out' is redundant.
5 / 5
The team followed the Keep a Changelog format to ___ release notes in a consistent, machine-readable structure.
Structure release notes is the standard technical writing collocation for organising a changelog in a consistent and readable format. 'Format along' and 'organise around' are informal. 'Write out' is too generic.