Practise the standard verbs for versioning and reviewing runbook changes.
0 / 5 completed
1 / 5
Fill in: 'We ___ every runbook change under version control, rather than an edit nobody's actually tracked back to a reason.'
We 'put a change under control' — the standard, simple collocation for versioning runbook edits like code. The other options are less idiomatic here.
2 / 5
Fill in: 'An untracked runbook edit made mid-incident can ___ the next on-call engineer following a step nobody's actually reviewed.'
We say an untracked edit will 'leave' the next engineer following an unreviewed step — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a changelog entry for every runbook revision, rather than an update nobody's actually explained the reasoning for.'
We 'add a changelog entry' — the standard, simple collocation for documenting why a runbook was revised. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every runbook edit against peer review before merging, rather than a step nobody else on-call's actually approved.'
We 'check an edit' — the standard, simple collocation for getting a runbook change reviewed before it's live. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ runbook version history quarterly for drift, rather than a doc nobody's actually compared to the live system.'
We 'audit history' — the standard, simple collocation for checking a runbook's versions still reflect reality. The other options aren't idiomatic here.