An engineer needs to flag an urgent issue. Which version is most appropriate for a Slack message to the team?
Option B is correct for Slack. Slack messages in engineering teams use: lowercase, abbreviations ("db"), contractions, direct language, and no formal structure. It signals urgency without being overly formal or creating unnecessary alarm. Option A is appropriate for an incident report or executive email — far too formal for a team Slack message. Option C is acceptable but more formal than natural Slack register. Option D is appropriate for a major incident alert, not a preliminary investigation message.
2 / 27
The same engineer then writes the post-incident report. Which version is most appropriate?
Option C is correct for a postmortem report. Formal incident reports include: specific timestamps (UTC), metric values (P99 latency), technical precision (commit hash), passive or nominative constructions, and complete sentences. Option A uses inappropriate informal language (lol, "went weird"). Option B lacks specific detail. Option D uses complete sentences but lacks the precision required for a technical incident record.
3 / 27
An engineer writes a code comment. Which version is most appropriate?
Option B is correct. Code comments should be: precise, explanatory of constraints or assumptions, and professional — without being overly formal. "Assumes single-threaded access; concurrent calls require a mutex" is a valuable technical constraint that prevents bugs. Option A is unprofessional. Option C is too verbose and subjective. Option D is too vague — it identifies a problem but provides no information about what the fix should be.
4 / 27
An architect is writing an ADR (Architecture Decision Record). Which opening sentence is most appropriate?
Option C is correct for an ADR. Architecture Decision Records require: formal register, complete sentences, precise technical vocabulary, and structured information. Option C explains what was decided, why, and what the future plan is. Option A is inappropriate informal register. Option B is too brief and lacks context. Option D uses a note-taking format inappropriate for a formal decision record.
5 / 27
A developer advocate is giving a conference talk and wants to introduce the concept of eventual consistency. Which opening is most appropriate?
Option B is correct for a conference talk. Technical presentations to practitioners should: use relatable analogies, be engaging and conversational, and build intuition before precision. Option A is a textbook definition — accurate but dry for a talk opening. Option C is too academic and references prior knowledge the audience may not have. Option D is a bullet-point format — inappropriate for spoken presentation.
6 / 27
Which message is MOST appropriate to send to an external enterprise client about a planned maintenance window?
Option B is correct for external client communication. External enterprise clients expect: formal register, specific dates and times with time zones, precise scope of impact, and actionable recommendations. Option A is appropriate for an internal Slack channel, not a client. Option C omits the formal framing and actionable context. Option D is too vague and informal for a client notification.
7 / 27
Which sentence best suits a README installation section?
Option C is correct. README installation sections should be: imperative ("Run"), concise, technically precise (with code formatting for the command), and direct. Option A is conversational and includes filler ("just", "pretty straightforward") — appropriate for a tutorial intro, not a reference section. Option B is excessively formal and uses passive nominalisation inappropriate for an instruction. Option D is too terse — it works as a bullet point but not as prose documentation.
8 / 27
A developer writes an error message for end users. Which version is most appropriate?
Option C is correct for an end-user error message. User-facing error messages should be: in plain language (no stack traces), empathetic, actionable, and helpful. Option A exposes internal implementation — a security and UX problem. Option B is too vague to be helpful. Option D is too technical for a general user but would be acceptable in a developer-facing API error response.
9 / 27
In a sprint standup, an engineer says they are blocked. Which phrasing is most appropriate?
Option B is correct for a standup. Standups should be: concise, clear, professional but conversational — not overly formal. "I'm blocked — I need X before I can do Y" is the natural standup format. Option A is too formal for a standup (nominalisations, passive). Option C is note-taking style — appropriate for standup notes, not spoken standup. Option D is imprecise and potentially blame-y in phrasing ("hasn't done their bit").
10 / 27
Which pair of sentences demonstrates the CORRECT register shift from Slack to a formal incident summary?
Option B is correct. It demonstrates the appropriate register shift: the Slack message uses informal, conversational language ("throwing 500s", "investigating now") appropriate for rapid internal communication. The formal summary uses complete sentences, specific timestamps, technical precision (HTTP 500), and passive/nominative constructions. Option A makes no register shift. Option C uses a crisis Slack message but the summary is too brief for a formal record. Option D maintains informal language in the summary ("having issues" is too vague).
11 / 27
Liam, a junior developer, needs to quickly inform the team about a critical bug discovered during testing of the new authentication service. Which Slack message would be most appropriate for this situation?
The first option uses informal language ('weird issue', 'Need your help!') and lacks specific details. Option 2 employs formal phrasing suitable for a critical alert, clearly stating the problem and its urgency. Options 3 and 4 are too abrupt and lack professionalism. This demonstrates understanding of shifting to a more direct and informative register when communicating urgent technical issues.
12 / 27
Sarah, an experienced architect, is drafting a post-incident report detailing the outage affecting the payment processing system. Which sentence would be most appropriate to open this document?
Option 1 is overly casual and doesn't convey the seriousness of the event. Option 2 utilizes formal language, acknowledging the investigation process and clearly stating the affected infrastructure. Options 3 and 4 are too vague and lack a professional tone. This highlights the importance of adopting a formal register when documenting incidents for stakeholders.
13 / 27
David is writing a code comment to explain a complex algorithm within a Python function. Which phrasing would be most appropriate?
Option 1 is completely meaningless and demonstrates a lack of technical clarity. Option 2 provides a precise description of the algorithm's purpose. Options 3 and 4 are overly informal and don't contribute to understanding the code. A formal comment should offer clear, concise explanations suitable for other developers reviewing the code.
14 / 27
Liam, a junior developer, needs to quickly inform the team about a critical bug discovered during testing of the new authentication service. Which Slack message would be most appropriate for this situation?
The first option uses informal language ('weird issue', 'Need your help!') and lacks specific details. Option 2 employs formal phrasing suitable for a critical alert, clearly stating the problem and its urgency. Options 3 and 4 are too abrupt and lack professionalism. This demonstrates understanding of shifting to a more direct and informative register when communicating urgent technical issues.
15 / 27
Sarah, an experienced architect, is drafting a post-incident report detailing the outage affecting the payment processing system. Which sentence would be most appropriate to open this document?
Option 1 is overly casual and doesn't convey the seriousness of the event. Option 2 utilizes formal language, acknowledging the investigation process and clearly stating the affected infrastructure. Options 3 and 4 are too vague and lack a professional tone. This highlights the importance of adopting a formal register when documenting incidents for stakeholders.
16 / 27
David is writing a code comment to explain a complex algorithm within a Python function. Which phrasing would be most appropriate?
Option 1 is completely meaningless and demonstrates a lack of technical clarity. Option 2 provides a precise description of the algorithm's purpose. Options 3 and 4 are overly informal and don't contribute to understanding the code. A formal comment should offer clear, concise explanations suitable for other developers reviewing the code.
17 / 27
Liam, a junior developer, needs to quickly inform the team about a critical bug discovered during testing of the new authentication service. Which Slack message would be most appropriate for this situation?
The first option uses informal language ('weird issue', 'Need your help!') and lacks specific details. Option 2 employs formal phrasing suitable for a critical alert, clearly stating the problem and its urgency. Options 3 and 4 are too abrupt and lack professionalism. This demonstrates understanding of shifting to a more direct and informative register when communicating urgent technical issues.
18 / 27
Sarah, an experienced architect, is drafting a post-incident report detailing the outage affecting the payment processing system. Which sentence would be most appropriate to open this document?
Option 1 is overly casual and doesn't convey the seriousness of the event. Option 2 utilizes formal language, acknowledging the investigation process and clearly stating the affected infrastructure. Options 3 and 4 are too vague and lack a professional tone. This highlights the importance of adopting a formal register when documenting incidents for stakeholders.
19 / 27
David is writing a code comment to explain a complex algorithm within a Python function. Which phrasing would be most appropriate?
Option 1 is completely meaningless and demonstrates a lack of technical clarity. Option 2 provides a precise description of the algorithm's purpose. Options 3 and 4 are overly informal and don't contribute to understanding the code. A formal comment should offer clear, concise explanations suitable for other developers reviewing the code.
20 / 27
Context: As a senior backend engineer, you're reviewing a pull request submitted by a junior developer. The PR introduces a new API endpoint for retrieving user profiles. The developer has used the phrase 'Let's just throw this out there...' in the code review comment. Which response is MOST appropriate to address this comment?
The developer's comment is too informal and lacks technical precision for a code review. Option 1 provides constructive feedback on error handling. Option 2 directly addresses the inappropriate tone, teaching the importance of professional communication in development. Options 3 & 4 are overly enthusiastic and don't address the register issue.
21 / 27
Alex is drafting a Slack message to his team about a potential performance bottleneck he's identified in the new microservice. Which of the following options best reflects an appropriate, informal tone for this internal communication?
Option 1 uses casual language ('Hey team,' 'Let's dig into why') and acknowledges the issue without immediately sounding overly formal or critical. Options 2, 3, and 4 are too rigid and utilize unnecessarily complex phrasing for an internal Slack discussion. The goal is to quickly alert the team while maintaining a collaborative, approachable tone.
22 / 27
Maria, a Senior DevOps Engineer, is writing a pull request description for a deployment script. Which of the following statements best demonstrates appropriate formal register?
Option 1 uses informal language ('Just ran,' 'looks good') which is unsuitable for a formal PR description. Option 2 clearly and precisely describes the script's purpose and functionality using technical terminology. Options 3 and 4 are too casual and lack detail – a formal description needs to be precise and informative.
23 / 27
John, a senior backend engineer, is reviewing a pull request submitted by Ben, a junior developer. Ben has added the following comment to his code:
```python
# This is pretty cool!
```
Which of the following responses would be most appropriate for John to add as a code review comment?
This scenario tests understanding of formal register when providing feedback on code. Option 1 is too informal and suggests a problem with a metric. Option 2 demonstrates a polite and constructive approach, prompting further explanation – exactly what's needed in a professional setting. Options 3 and 4 are overly critical and could be perceived as dismissive. The goal here is to encourage clarification without immediately pointing out potential issues.
24 / 27
Maya, a product manager, needs to send an email to the development team announcing a change in requirements for Feature X. Which of the following sentences best demonstrates appropriate formal register?
This question assesses the ability to use precise language in a business context. Option 1 is overly casual and lacks professionalism. Option 2 uses formal phrasing suitable for conveying important information about requirements changes. Options 3 and 4 are too informal and lack clarity regarding the nature of the change.
25 / 27
David is drafting an API response for a new user registration endpoint. The response should include the newly created user's ID. Which of the following JSON responses would be most appropriate in a Slack message to announce this change?
This tests the ability to communicate technical details clearly and concisely in an informal setting. Option 1 provides a technically correct JSON response, suitable for API documentation or automated systems. Option 2 is appropriate for Slack, clearly stating the change. Options 3 and 4 are not valid JSON and would be inappropriate for a Slack announcement.
26 / 27
Alex is writing a PR description for a change that improves the performance of a database query. Which sentence would be most appropriate to start this document?
This focuses on the opening statement of a PR description. Option 1 is too informal and lacks detail. Option 2 provides a formal and informative introduction to the change, outlining the benefit (performance improvement). Options 3 and 4 are overly casual and don't adequately describe the work done.
27 / 27
Mark, a senior software engineer, is responding to a code review comment from Emily on a new feature for the e-commerce platform. Emily's comment reads: 'This logic is a bit messy, can't you just make it simpler?' Which of the following responses would be most appropriate in a formal email to Emily?
This scenario tests understanding of formal register when receiving critique. Option A acknowledges the feedback constructively and proposes a solution. Options B & C are dismissive and informal, inappropriate for a professional setting. Option D directly contradicts the reviewer without offering a reasoned explanation – it's too confrontational. The correct response demonstrates respectful engagement.
What will I practise in "Formal vs Informal Register in IT English — Grammar Exercise"?
Practice adapting English register to context: technical specs vs Slack messages vs architecture docs vs code comments — choosing the right level of formality.
How many exercises are in this module?
This module has 27 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.