5 exercises — matching register to context: formal documentation, PR comments, Slack messages, client emails, and architectural records.
0 / 18 completed
1 / 18
A senior engineer needs to report a production incident to the CTO. Which version uses the appropriate register?
Option B uses the correct formal register for executive reporting. It includes: precise timestamps, named roles (on-call team), quantified impact (48 minutes downtime), and a follow-up action (postmortem). Option A is Slack-register — appropriate for team channels but not for CTO communication. Option C is overly brief and lacks facts. Option D is an alert-format, not a report. Register mapping for IT communication: Slack/Teams → casual, emoji allowed, abbreviations fine; Email to manager → semi-formal, structured; Incident report / postmortem → formal, passive voice acceptable, timestamps required; Executive briefing → formal, impact-focused, action-oriented.
2 / 18
A developer is writing a PR description. Which register is most appropriate?
Option B strikes the correct balance for a PR description: it references the issue number, names the component (AuthService), explains the mechanism (null check), and mentions test coverage — without being overly casual or bureaucratically formal. Option A is too casual — PR descriptions are permanent technical records. Option C is excessively formal — PR prose should be clear, not legalistic. Option D is too terse — it provides no context for reviewers or future readers. PR register principle: semi-formal + specific. Think of it as a technical memo to your team, not a chat message or a legal document.
3 / 18
A colleague asks on Slack: "why does the API return 401 sometimes on valid tokens lol". You respond in a Slack thread. Which response is in the right register?
Option B matches the Slack register: casual tone, lowercase, no full stops, offers a diagnosis (clock skew), gives a reason (JWT exp sensitivity), and asks for information to proceed. It is helpful and appropriately informal. Option A is too formal for Slack — the elaborate noun phrase sounds robotic in a chat context. Option C cites a specification and references a runbook — completely wrong register for a casual Slack question. Option D is overly bureaucratic and unhelpful for a quick chat. Key Slack register markers: contractions, lowercase acceptable, emojis optional, sentence fragments OK, quick action or question at the end.
4 / 18
You need to email a client about an upcoming API breaking change. Which register is correct?
Option B is correct for a client-facing formal email. It uses a formal opening, specifies the exact release date and endpoint, includes a migration guide reference, and provides the deprecation deadline. Option A uses "heads up" twice — this is Slack language and sounds unprofessional in a client email. Option C is too terse — clients need context, not bullet points in prose form. Option D uses all-caps which reads as shouting and creates alarm without substance. Client email register rules: formal salutation (omitted here for brevity), complete sentences, concrete dates and action items, professional close, attachments referenced explicitly.
5 / 18
A tech lead writes a comment in an Architecture Decision Record (ADR). Which register is most appropriate?
Option B is correct for an ADR. ADRs are long-lived technical records — they must be formal, evidence-based, and auditable. The correct register includes: the passive construction ("was selected"), quantified criteria (100k messages/second), named trade-offs (push-based model, no replay), and a reference to evidence (benchmark file). Option A uses "tbh" (to be honest) — this informal marker is inappropriate in a permanent technical document. Option C expresses an opinion, not a reasoned decision. Option D is factually thin — "It is fast" cannot justify an architectural choice. ADR register: semi-formal prose, passive or impersonal constructions, quantified criteria, referenced evidence, clear decision and rationale.
6 / 18
Alex from the Backend Team needs to quickly inform Sarah, the DevOps Lead, about a suspected database connection leak impacting production. Which of the following messages best reflects the appropriate register for this urgent notification?
Option A: "Hi Sarah, we're seeing some unusual activity in the database logs. Could you take a look when you have a moment?"
Option B: "Sarah, there's a severe database connection issue impacting production! Immediate investigation required – potential service degradation."
Option C: "Hey Sarah, just wanted to let you know we're monitoring the database. Everything seems okay so far."
Option D: "Regarding the DB, we've identified a possible connection leak and are escalating for immediate triage."
This situation demands directness and urgency due to a production issue. Option B is too informal ('lol') and doesn't convey the seriousness. Option C is passive and unhelpful. Option D correctly uses formal language appropriate for reporting a critical incident to a DevOps lead – it's clear, concise, and emphasizes the required action.
7 / 18
Chloe receives this Slack message from a teammate: "why does the API return 401 sometimes on valid tokens lol". You respond in a Slack thread. Which response is in the right register?
Option A: "That's strange! Maybe there's an issue with the token itself?"
Option B: "The 401 status code indicates authentication failure. Double-check that the token is correctly formatted and has not expired."
Option C: "lol, yeah, it happens sometimes! Just keep trying."
Option D: "It's likely a temporary issue with our API servers. We should investigate further if this persists."
Slack conversations often benefit from direct explanations, especially when debugging. Option A is vague and unhelpful. Option C uses informal language and doesn't offer a solution. Option D is slightly better but lacks the immediate clarity needed in a Slack response. Option B provides a precise explanation of the 401 error code and directs the teammate to troubleshoot.
8 / 18
Alex from the Backend Team needs to quickly inform Sarah, the DevOps Lead, about a suspected database connection leak impacting production. Which of the following messages best reflects the appropriate register for this urgent notification?
Option A: "Hi Sarah, we're seeing some unusual activity in the database logs. Could you take a look when you have a moment?"
Option B: "Sarah, there's a severe database connection issue impacting production! Immediate investigation required – potential service degradation."
Option C: "Hey Sarah, just wanted to let you know we're monitoring the database. Everything seems okay so far."
Option D: "Regarding the DB, we've identified a possible connection leak and are escalating for immediate triage."
This situation demands directness and urgency due to a production issue. Option B is too informal ('lol') and doesn't convey the seriousness. Option C is passive and unhelpful. Option D correctly uses formal language appropriate for reporting a critical incident to a DevOps lead – it's clear, concise, and emphasizes the required action.
9 / 18
Chloe receives this Slack message from a teammate: "why does the API return 401 sometimes on valid tokens lol". You respond in a Slack thread. Which response is in the right register?
Option A: "That's strange! Maybe there's an issue with the token itself?"
Option B: "The 401 status code indicates authentication failure. Double-check that the token is correctly formatted and has not expired."
Option C: "lol, yeah, it happens sometimes! Just keep trying."
Option D: "It's likely a temporary issue with our API servers. We should investigate further if this persists."
Slack conversations often benefit from direct explanations, especially when debugging. Option A is vague and unhelpful. Option C uses informal language and doesn't offer a solution. Option D is slightly better but lacks the immediate clarity needed in a Slack response. Option B provides a precise explanation of the 401 error code and directs the teammate to troubleshoot.
10 / 18
David from the Frontend team is writing a comment on a code review for Jane's pull request. The PR introduces a new component that uses a third-party charting library. Jane has already mentioned the potential performance impact in the PR description. Which of the following comments best aligns with professional technical communication?
The appropriate register here is one that encourages further investigation and data-driven decision-making. Simply stating 'Nice work!' or 'Just a minor change' doesn't address Jane's previous concern about performance. Option 2 demonstrates a proactive approach to risk mitigation and aligns with best practices for code reviews – asking for quantifiable evidence.
11 / 18
Mark from the Infrastructure team sends this message to the #devs Slack channel: "Fixed that weird timeout issue. Turns out it was a simple DNS misconfiguration. 😎". Which of the following best describes Mark's register? (Hint: Consider the level of formality and detail suitable for a public development channel.)
Mark's message utilizes informal language ('weird', 'turns out'), an emoji, and avoids overly technical jargon. This register is appropriate for a general development channel where quick updates are common. The key here is the relaxed tone – a formal report would require far more detail and precise terminology. Options A and C are too rigid; option D is unnecessarily complex.
12 / 18
Liam is writing a PR description for a change that refactors a large function into smaller, more manageable components. He writes: "This commit improves code readability and maintainability by breaking down the monolithic function into several independent modules." Which of the following is the MOST appropriate register for this scenario? (Consider the audience – other developers reviewing the PR.)
Liam's description uses precise technical language – 'refactors,' 'monolithic function,' 'independent modules,' and 'maintainability.' This level of detail is suitable for a PR review where other developers need to understand the technical implications of the change. Option A is overly verbose and marketing-like; option C is too informal; and option D discusses unrelated aspects (server capacity).
13 / 18
John from the QA team sends this message to Mark, a developer, via Slack: "This bug is *totally* broken! Seriously, it's failing everywhere. Just fix it!". Which option best describes the register used in John's message?
This message uses informal language ('totally broken,' 'seriously'), excessive exclamation marks, and direct emotional expression. This is inappropriate for a professional communication within a development team, especially when reporting a bug. The correct answer reflects the overly casual tone used.
14 / 18
Emily, a senior developer, is writing a comment on a code review for a colleague's PR that introduces a new feature. She writes: "The implementation of the authentication flow is robust and utilizes best practices for security. Further testing is recommended to ensure full coverage.". Which aspect of register does this comment primarily demonstrate?
Emily's comment is clear, concise, and provides constructive feedback. It focuses on key aspects like security and testing—common concerns in code reviews—and suggests a logical next step. The language is professional and avoids overly complex or subjective phrasing.
15 / 18
David, the API developer, receives this response from his monitoring system: `HTTP 500 Internal Server Error - Transaction ID: TXN-4789. Traceback: ...`. He responds to his team channel with: 'Ugh, another 500? What's going on?!'. Which of the following best describes David's use of register?
While the error message itself requires a factual response, David's follow-up is too informal. Using 'Ugh' and 'What's going on?!' is not suitable when communicating about an internal server error; it lacks professionalism. The correct answer reflects a more measured approach to conveying information.
16 / 18
Rajesh from the Security team needs to alert the development team about a potential vulnerability discovered during automated scanning of a new API endpoint. He writes in a Slack channel: 'OMG, found a HUGE security hole! Seriously, fix this ASAP!' Which response best reflects the appropriate register for Rajesh's message?
Rajesh's message uses overly casual language ('OMG', 'huge hole', 'fix this ASAP') which is inappropriate for communicating technical issues to colleagues, especially in a security context. A formal and precise register is needed to convey the severity of the vulnerability and direct action. The correct response clearly outlines the problem and expected next steps – demonstrating professionalism and prioritizing urgency.
17 / 18
Sarah, a DevOps engineer, needs to inform the development team about an unexpected outage affecting a critical microservice. She sends a message in a dedicated incident channel: 'Service X is down! No idea why yet…'. Which of the following best describes the register used in Sarah's message?
Sarah's message utilizes informal language and avoids specific details about the outage. While understandable in an initial notification, this register is unsuitable for a critical incident. The correct response provides clear, concise information – essential for effective communication during a service disruption.
18 / 18
Maria from the Data Engineering team is participating in a standup meeting. She updates the team on her progress: 'I've finished building the new data pipeline and it's running smoothly! Everything's looking good.' Which register does Maria employ?
Maria's response is a standard standup update. It provides a concise summary of her accomplishments and confirms operational status. Option A uses precise language suitable for a technical update – it avoids hyperbole and focuses on factual information. Options B and C are too informal; option D lacks specifics.
What will I practise in "Register Shifts in Technical Communication — Grammar Exercise"?
Practice using the correct register for documentation, Slack, email, PR descriptions, and ADRs. 5 interactive grammar exercises for IT professionals.
How many exercises are in this module?
This module has 18 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.