Practise the standard verbs for keeping an OpenAPI spec honest.
0 / 5 completed
1 / 5
Fill in: 'We ___ the OpenAPI spec against the running service so the documented contract never quietly drifts.'
We 'validate a spec' — the standard collocation for confirming it still matches real behaviour. The other options aren't idiomatic here.
2 / 5
Fill in: 'A hand-edited response example can ___ out of sync with the actual field names returned by the API.'
We say documentation can 'fall' out of sync — the standard, natural collocation for gradual drift. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the spec from annotated code instead of maintaining a separate YAML file by hand.'
We 'generate a spec' — the standard, established collocation for producing documentation automatically. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a breaking schema change in CI before it ever reaches a published contract.'
We 'catch' a change — the standard collocation for detecting an issue before it escapes. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ consumers of an upcoming breaking change well before the new contract actually ships.'
We 'notify' consumers — the standard, simple collocation for informing API clients in advance. The other options are less idiomatic here.