5 exercises — passive structures for system docs, API references, status messages, and change logs.
0 / 5 completed
1 / 5
Choose the correct passive form: "The API gateway _____ all incoming requests before they reach the service."
Present simple passive "is routed" describes a permanent system behaviour where the focus is on what happens to requests (the agent — the gateway — is already stated, so passive works here). In API documentation, the passive voice is preferred when describing what happens to data or requests.
2 / 5
Which sentence correctly describes a completed system change?
Past simple passive "was updated" is correct for a completed action at a specific past time ("last night"). The present simple passive would describe an ongoing process; the present perfect would omit the specific time reference.
3 / 5
Complete the status message for a CI/CD pipeline: "Build #142 _____ successfully. All 847 tests _____."
Present perfect passive "has been completed / have been run" is ideal for status messages that report recent completed actions with present relevance. This tense is commonly used in CI/CD dashboards, deployment notifications, and build reports.
4 / 5
An engineer is writing release notes. Choose the best passive sentence:
"Has been deprecated" (present perfect passive) is the standard phrasing in release notes and API changelogs. It reports a recent change with ongoing consequences (developers must migrate). Professional API documentation uses this pattern consistently: "X has been deprecated / removed / renamed."
5 / 5
Choose the passive form that correctly describes a scheduled automated process: "Backups _____ every night at 02:00 UTC and _____ to the object storage bucket."
Both verbs need present simple passive ("are run / are transferred") because this describes a recurring automated process. When documenting scheduled tasks, cron jobs, or automated pipelines, present simple passive is used for both the trigger action and subsequent steps in the same process chain.