5 exercises — overly formal English in technical documents sounds unnatural to native speakers. These exercises train you to recognise which phrasal verb makes a sentence sound professional without being bureaucratic.
Phrasal verbs that replace formal equivalents
phase out = gradually discontinue (not "terminate progressively")
look into = investigate (not "conduct an investigation of")
kick off = initiate / begin a planned event (not "commence")
tear down = decommission cloud resources (not "permanently remove")
run through = present/review methodically (not "provide a comprehensive explanation of")
0 / 10 completed
1 / 10
Formal sentence from a project document:
"The engineering team will gradually discontinue the legacy SSO module throughout Q2, transitioning all services to the new OAuth 2.0 provider."
Which rewrite uses the most natural professional phrasal verb?
"Phase out" is the natural phrasal verb equivalent of "gradually discontinue." It carries the same meaning — scheduled, incremental removal — but sounds significantly more natural in professional IT communication, runbooks, and migration plans. "Terminate" is formal and used for processes or contracts, not software libraries. "Delete" is abrupt and implies immediate removal, not gradual. "Retire" is used but is more formal and slightly HR-flavoured (retiring a system or a person). "Phase out" is the go-to term in engineering: "we're phasing out the monolith", "the API will be phased out in six months", "phase-out timeline".
2 / 10
Formal sentence from a bug report:
"Please conduct a thorough investigation of the reported intermittent memory allocation failure before the commencement of the next sprint."
Which rewrite uses the most natural professional phrasal verb?
"Look into" is the natural phrasal verb for "investigate" in professional IT communication. It is the most common choice in Jira tickets, Slack messages, stand-up notes, and post-mortems: "can someone look into this?", "I'll look into the root cause", "we need to look into why this is intermittent". The level of formality is ideal for internal communication — professional but not bureaucratic. "Examine" and "analyse" are correct but feel clinical and academic rather than operational. "Research" implies an open-ended inquiry rather than a specific bug investigation. "Look into" = investigate a specific problem; "look at" = review/check (less intense). Always prefer "look into" when the goal is finding the cause of a specific issue.
3 / 10
Formal sentence from a release plan document:
"The production deployment will be initiated at 02:00 UTC on Friday, following completion of all pre-deployment verification steps."
Which rewrite uses the most natural professional phrasal verb?
"Kick off" is the standard phrasal verb for "initiate/begin" a planned, coordinated activity in professional tech teams. It has the right register for a deployment plan — professional but not stuffy. Usage: "the deployment kicks off at 02:00", "we'll kick off the migration next Tuesday", "kick off the release pipeline". The noun form is also common: "the kickoff meeting", "before the sprint kickoff". "Begin" and "start" are correct but neutral — they don't carry the sense of a coordinated, scheduled event. "Commence" is overly formal — it belongs in legal documents and official announcements, not engineering plans. "Kick off" signals: this is a planned, team effort with a defined start.
4 / 10
Formal sentence from a post-demo checklist:
"Following the successful demonstration, all temporary cloud provisioning resources must be decommissioned and permanently removed."
Which rewrite uses the most natural professional phrasal verb?
"Tear down" is the specific DevOps/infrastructure term for permanently destroying provisioned cloud resources — exactly what "decommissioned and permanently removed" means. It is the standard vocabulary in IaC, deployment pipelines, and cloud cost management. Usage: "tear down the staging environment", "the teardown script", "auto-teardown after 24 hours". "Clean up" implies removing leftover files, cached data, or temporary artifacts — not destroying infrastructure. "Delete" and "remove" are too generic — they describe single-resource operations, not the complete destruction of an environment. When a DevOps engineer says "tear down the stack", every team member understands this means: all resources gone, no cloud costs remain.
5 / 10
Formal sentence from a presentation agenda:
"The principal architect will present a comprehensive explanation of the proposed system design to all stakeholders prior to the commencement of the implementation phase."
Which rewrite uses the most natural professional phrasal verb?
"Run through" is the natural phrasal verb for "present/review comprehensively" in a professional context. It specifically implies a structured, sequential walkthrough — not just showing or explaining, but taking the audience through each part methodically. Usage: "let me run through the design", "we'll run through the architecture tomorrow", "run through the deployment checklist before go-live". This is the standard phrasing for design reviews, sprint demos, architecture presentations, and technical walkthroughs. "Explain" is generic. "Show" is too casual and visual. "Discuss" implies a two-way conversation rather than a structured presentation. "Run through" signals: "I will guide you through this systematically from start to finish."
6 / 10
Liam (Senior Dev) posted in the #devops Slack channel: 'We need to roll back the database migration. It's causing major performance issues.' Which of the following is the most natural way for Mark (Junior Dev) to respond?
The core of the situation is an urgent rollback request. Option 3 reflects a direct and actionable response – immediately reverting to the previous backup is the standard procedure in this scenario. Options A and B are too detailed for an initial reaction, while option C introduces unnecessary questioning that delays the critical action. It's important to prioritize immediate problem resolution over lengthy investigations when urgency is present.
7 / 10
Sarah (Code Reviewer) comments on a PR: 'This code introduces a potential race condition. Consider using a mutex to synchronize access to the shared resource.' Which phrase best captures Sarah's concern in a more natural, less formal way?
Sarah's comment highlights a serious issue – potential data corruption. Option 2 directly and clearly describes the risk associated with the race condition. While options A, C, and D are technically correct, they are overly formal and less immediately understandable for someone reviewing code. Framing it around 'data corruption' is more impactful and aligns better with common developer discussions.
8 / 10
David (Release Manager) writes in the release notes: 'The deployment will commence at 06:00 EST on Thursday. Ensure all pre-flight checks are completed before initiating.' Which of the following is the most appropriate revision for improved clarity?
The original phrasing is overly formal and slightly confusing. Option 1 offers a clear and concise instruction with more natural language – 'verify all prerequisites beforehand.' It avoids jargon like 'pre-flight checks' which can be ambiguous. The other options are either too verbose or lack specific direction.
9 / 10
Maria (Product Owner) says in a standup update: 'We're resolving the intermittent API throttling. It's impacting user experience.' What is the best way for Ben (Developer) to elaborate on this issue?
Maria's statement indicates a problem with throttling. Option 2 directly explains *why* the throttling is impacting the user experience – 'the rate limiting mechanism is failing.' The other options describe related concepts but don't pinpoint the core issue as clearly. Using language about 'errors for users' provides context and urgency.
10 / 10
John (Tech Lead) writes in a PR description: 'The service will be upgraded to the latest version of Kubernetes.' Which phrase best expresses this change in a more natural and informative way?
Option 3 provides a clear and concise explanation of the upgrade. It focuses on the benefits – 'improved scalability' – which is a common reason for upgrading Kubernetes. The other options are overly verbose or use unnecessarily complex terminology, making it less approachable for a broader audience. It's about communicating *why* the change is being made.
What will I practise in "Register Transformation: Formal → Natural"?
This module focuses on Phrasal Verbs — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasal Verbs exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasal verbs — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasal Verbs exercises?
See the Phrasal Verbs hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.