Phrasal Verbs vs Latinate Alternatives in Technical Docs
5 exercises — choosing between "set up" and "configure", "look into" and "investigate" in READMEs, API specs, incident reports, and Slack messages.
0 / 15 completed
1 / 15
A developer is writing a user-facing README. Which sentence uses the most appropriate register?
"Set up" is the correct choice for a user-facing README. Phrasal verbs like set up, run, log in, sign up are natural and conversational — ideal for guides aimed at developers of all levels. "Execute" and "configure" (Latinate) are appropriate in internal or formal documentation but can feel stiff in a README. "Utilise" and "initialise" are unnecessarily formal for a simple instruction. "Procure" is a commercial/legal term inappropriate here. The register rule: use phrasal/simple verbs for instructions; use Latinate alternatives in technical specs and formal reports.
2 / 15
An architect is writing a formal API specification. Which phrasing is most register-appropriate?
"Exposes user data retrieval functionality" is most appropriate for a formal API specification. Latinate/technical verbs such as expose, retrieve, authenticate, validate, invoke carry precision and formality that suits reference documentation. "Lets you get" and "can use… to pull" are phrasal and conversational — better suited to tutorials or blog posts. "Gives out" is too informal for any technical document. Understanding when to use phrasal verbs (informal, instructional) vs Latinate alternatives (formal, reference) is a core register skill for IT professionals.
3 / 15
Which pair correctly matches a phrasal verb with its Latinate alternative used in technical documentation?
"Find out → discover" and "get rid of → eliminate" are accurate register equivalents used in IT writing. In documentation you replace "find out the root cause" with "identify / determine / ascertain the root cause"; "get rid of technical debt" becomes "eliminate / reduce / address technical debt." Option B: "negate" means to make negative, not to turn off (use "disable" or "deactivate"). Option C: "employ" means to use/hire, not to set up; "archive" means to store, not bring down a service (use "decommission" or "take offline"). Option D: "initiate" is the opposite of shut down; use "terminate" or "stop."
4 / 15
A technical writer revises a draft. The original says: "The system will come up again after the database comes back." The revised version should read:
"Resume operations after the database recovers") replaces both phrasal verbs (come up again, comes back) with precise Latinate-register alternatives (resume, recover) appropriate for technical documentation. Option A: "restores" is intransitive here — "the database restores" is incorrect without an object; use "the database is restored" or "the database recovers." Option B: partially fixes the problem but keeps "comes back online" — acceptable but slightly mixed register. Option D: "goes back to work" and "gets fixed" are too conversational for formal documentation.
5 / 15
A Slack message to a teammate reads: "Can you look into why the Kafka consumer is falling behind?" Which version is appropriate for a formal incident report?
"Please investigate the root cause of Kafka consumer lag" uses the Latinate verb investigate and the precise technical noun phrase root cause of Kafka consumer lag — appropriate for a formal incident report or post-mortem action item. "Look into" (options A and C) is a phrasal verb suitable for informal Slack messages but not for formal documents. "Have a look at" (option D) is similarly informal. Incident reports are archived, referenced in SLA reviews, and reviewed by stakeholders — formal register is expected. The rule: register follows audience and permanence.
6 / 15
Alex, a senior engineer, is writing a comment on a code review for a colleague. The code snippet handles error logging. Which phrasing best reflects professional technical communication?
A) 'The thing just crashed and burned!'
B) 'The system encountered an exception; we should investigate.'
C) 'This is totally messed up, fix it!'
D) 'It failed to execute properly.'
Option A uses overly informal and emotive language unsuitable for a code review. While 'crashed' is technically accurate, it lacks precision. Option B employs a standard Latinate phrase – 'encountered an exception' – expressing the error clearly and professionally. Options C and D are excessively casual and lack technical terminology. Using phrasal verbs like 'encounter' provides a more formal and precise way to describe the situation.
7 / 15
Ben is writing a pull request description for a change to a configuration file. The original draft reads: 'The server will come back online after it's rebooted.' Which revision best utilizes a phrasal verb and maintains professional tone?
A) 'The server should restart automatically after the reboot.'
B) 'The server will be available again following the reboot.'
C) 'Fix the server so it's online.'
D) 'Reboot the server.'
Option A correctly uses 'restart', a phrasal verb that clearly describes the process. It avoids overly simplistic phrasing. Option B offers a more formal alternative but still relies on a Latinate construction. Options C and D are instructions rather than descriptions – they lack formality appropriate for documentation. Using 'restart' provides a concise and professional way to convey the intended action.
8 / 15
Alex, a senior engineer, is writing a comment on a code review for a colleague. The code snippet handles error logging. Which phrasing best reflects professional technical communication?
A) 'The thing just crashed and burned!'
B) 'The system encountered an exception; we should investigate.'
C) 'This is totally messed up, fix it!'
D) 'It failed to execute properly.'
Option A uses overly informal and emotive language unsuitable for a code review. While 'crashed' is technically accurate, it lacks precision. Option B employs a standard Latinate phrase – 'encountered an exception' – expressing the error clearly and professionally. Options C and D are excessively casual and lack technical terminology. Using phrasal verbs like 'encounter' provides a more formal and precise way to describe the situation.
9 / 15
Ben is writing a pull request description for a change to a configuration file. The original draft reads: 'The server will come back online after it's rebooted.' Which revision best utilizes a phrasal verb and maintains professional tone?
A) 'The server should restart automatically after the reboot.'
B) 'The server will be available again following the reboot.'
C) 'Fix the server so it's online.'
D) 'Reboot the server.'
Option A correctly uses 'restart', a phrasal verb that clearly describes the process. It avoids overly simplistic phrasing. Option B offers a more formal alternative but still relies on a Latinate construction. Options C and D are instructions rather than descriptions – they lack formality appropriate for documentation. Using 'restart' provides a concise and professional way to convey the intended action.
10 / 15
Alex, a senior engineer, is writing a comment on a code review for a colleague. The code snippet handles error logging. Which phrasing best reflects professional technical communication?
A) 'The thing just crashed and burned!'
B) 'The system encountered an exception; we should investigate.'
C) 'This is totally messed up, fix it!'
D) 'It failed to execute properly.'
Option A uses overly informal and emotive language unsuitable for a code review. While 'crashed' is technically accurate, it lacks precision. Option B employs a standard Latinate phrase – 'encountered an exception' – expressing the error clearly and professionally. Options C and D are excessively casual and lack technical terminology. Using phrasal verbs like 'encounter' provides a more formal and precise way to describe the situation.
11 / 15
Ben is writing a pull request description for a change to a configuration file. The original draft reads: 'The server will come back online after it's rebooted.' Which revision best utilizes a phrasal verb and maintains professional tone?
A) 'The server should restart automatically after the reboot.'
B) 'The server will be available again following the reboot.'
C) 'Fix the server so it's online.'
D) 'Reboot the server.'
Option A correctly uses 'restart', a phrasal verb that clearly describes the process. It avoids overly simplistic phrasing. Option B offers a more formal alternative but still relies on a Latinate construction. Options C and D are instructions rather than descriptions – they lack formality appropriate for documentation. Using 'restart' provides a concise and professional way to convey the intended action.
12 / 15
Sarah, a junior developer, posted the following message to Slack: 'The API is throwing errors. Let's debug it!' Which phrasing best suits a formal incident report and demonstrates professional technical communication?
Using phrasal verbs like 'throwing' or 'debug' in a formal report can sound informal and potentially less precise. 'Returning errors' and 'investigate' are more professional alternatives that clearly state the problem and the intended action. The original option is acceptable for casual communication but not documentation.
13 / 15
David, a DevOps engineer, is writing an update for the daily standup. He needs to describe the status of a recent deployment. Which phrasing best communicates this concisely and professionally?
A) 'The application has been initiated successfully.'
B) 'The application is now running after the deployment.'
C) 'The application started up again after the rollout.'
D) 'The application is back online following the update.'
Phrasal verbs like 'started up' are more common and natural in technical discussions about deployments. While 'back online' is understandable, 'started up again' specifically refers to the action of the system becoming operational after a change. Option A is overly formal and less direct; option B is accurate but lacks the concise efficiency of a phrasal verb.
14 / 15
Emily, a software architect, is drafting an API specification. Which sentence uses the most appropriate phrasing for describing a function's behavior?
A) 'The system will bring up the data.'
B) 'The service returns the requested information.'
C) 'The server will come back with the results.'
D) 'The application is generating the output.'
In formal API documentation, precise and unambiguous language is crucial. 'Returns' clearly indicates the function's action—providing a result. Options A and C use less precise phrasal verbs; option D describes a process rather than an action of the API itself.
15 / 15
Mark is reviewing a pull request for a new feature. One of the comments reads: 'The server will come back online after it's rebooted.' Which revision best reflects professional technical communication and demonstrates an understanding of phrasal verbs?
This question tests understanding of replacing a less precise phrase with a more professional and technically accurate one. 'Come back online' is a common phrasal verb in this context, but a direct replacement provides clarity and precision. Options A & B are overly verbose, while option C misuses the terminology.
What will I practise in "Phrasal Verbs vs Latinate Alternatives in Technical Docs — Grammar Exercise"?
Practise choosing between phrasal verbs and Latinate alternatives for appropriate register in IT documentation and communication. 5 exercises.
How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.