5 exercises — learn when contractions are appropriate in Slack, error messages, code comments, pull requests, and technical documentation.
0 / 16 completed
1 / 16
A developer posts in a team Slack channel: "Hey, I've pushed the fix. It's on the feature branch — you'll need to pull and rebuild your containers." Which statement about the contractions is correct?
Contractions are entirely appropriate in Slack, Microsoft Teams, Discord, and other synchronous team chat tools. These are conversational, informal channels where matching spoken register builds rapport and reduces friction. Using full forms ("I have pushed", "It is on", "you will need") in chat reads as stiff and formal — potentially cold or even passive-aggressive to native English speakers. The "it's ambiguity" argument (Option D) is largely theoretical: context makes the meaning clear. Reserve full forms for formal writing: official documentation, security advisories, compliance reports, and company-wide announcements.
2 / 16
Which error message uses the most appropriate register for a production web application?
"We couldn't load this page" is the best choice: it uses a single, natural contraction ("couldn't") in a calm, helpful, and professional tone. Option A overdoes the reassurance ("Don't worry") and informality — the exclamation mark and "right now" sound flippant for an error state. Option B uses zero contractions, which makes it read as cold and bureaucratic — "Do not proceed" sounds like a warning sign. Option D ("Oops!", "We've lost this page") is too casual and "It doesn't exist anymore!" is slightly accusatory. Best error message practice: calm, actionable, one contraction level — neither overly cheerful nor robotic.
3 / 16
A developer is writing inline code comments for a shared codebase. Which comment style is most appropriate?
Both options A and B are used in professional codebases — the choice depends on team style. However, Option A is increasingly preferred in modern development culture: contractions in code comments create a natural conversational tone between developers and reduce reading friction. Major open-source projects (including parts of Node.js, React, and TypeScript) use contractions in comments. Option B is also valid, particularly in codebases with stricter style guides. Option C is too terse and loses explanatory context. Option D starts with "I've" — code comments should not be first-person ("I did X") as they become misleading after code ownership changes; prefer "Note:", imperatives, or third-person descriptions.
4 / 16
A developer is writing a pull request description for a feature branch targeting the main branch. Which opening is most appropriate?
PR descriptions occupy a middle register: more formal than chat, less formal than official documentation. Option B is ideal: third-person, no contractions, quantified outcome ("40%"), concise. It reads professionally and provides clear information for code reviewers and future `git log` readers. Option A (first-person, contractions, "You'll see") is too chatty for a PR — PRs are semi-permanent records read by many people, including future maintainers. Option C is a fragment-note, acceptable for WIP PRs but not final merges. Option D (no contractions, over-wordy) is unnecessarily formal. Rule: PR descriptions — no contractions, no first-person "I", quantify changes where possible.
5 / 16
Which sentence shows an appropriate difference in contraction use between a technical blog post and API reference documentation?
Option B correctly distinguishes the two registers. Technical blog posts are intentionally conversational — they address the reader directly ("You'll want to", "you're sending") and contractions create an engaging, approachable voice. API reference documentation, by contrast, is formal and imperative: it uses the second-person imperative without the informal "you'll want to" softener and avoids contractions for precision and translatability. API docs are consumed by developers worldwide (many reading in a second language) and often by automated tooling; formal, unambiguous prose serves that audience better. Option C reverses the registers — wrong. Option D reverses the contraction logic — wrong.
6 / 16
Sarah from the DevOps team sends this message in a Slack channel: ''We're gonna need to rollback that deployment. It's causing timeouts and impacting user experience.'
Which of the following best describes Sarah's language regarding contractions?
Sarah's use of 'gonna' is perfectly acceptable within a Slack channel for rapid updates and internal discussions. While strict grammatical rules might dictate 'going to,' informal language is often preferred when prioritizing speed and clarity in communications between developers. The key here is recognizing the relaxed register appropriate for this context, as opposed to more formal documentation.
7 / 16
Sarah from the DevOps team sends this message in a Slack channel: ''We're gonna need to rollback that deployment. It's causing timeouts and impacting user experience.'
Which of the following best describes Sarah's language regarding contractions?
Sarah's use of 'gonna' is perfectly acceptable within a Slack channel for rapid updates and internal discussions. While strict grammatical rules might dictate 'going to,' informal language is often preferred when prioritizing speed and clarity in communications between developers. The key here is recognizing the relaxed register appropriate for this context, as opposed to more formal documentation.
8 / 16
Sarah from the DevOps team sends this message in a Slack channel: ''We're gonna need to rollback that deployment. It's causing timeouts and impacting user experience.'
Which of the following best describes Sarah's language regarding contractions?
Sarah's use of 'gonna' is perfectly acceptable within a Slack channel for rapid updates and internal discussions. While strict grammatical rules might dictate 'going to,' informal language is often preferred when prioritizing speed and clarity in communications between developers. The key here is recognizing the relaxed register appropriate for this context, as opposed to more formal documentation.
9 / 16
John, a junior developer, posted this message to the team channel: 'I've just merged the branch. It's gonna be deployed soon.' Which of these options best reflects the most professional register for communication within a software development environment?
While contractions like 'gonna' are common in informal conversation, professional IT communication typically favors more formal phrasing. Using phrases like 'has been completed' and 'scheduled' demonstrates greater precision and respect for the audience. The incorrect options use overly casual language that could be perceived as unprofessional within a development team.
10 / 16
Liam, an API developer, received this response from the authentication service: `{"status": "error", "message": "Insufficient permissions. User 'dev123' lacks access to endpoint /users/profile."}`. Which of the following statements about register and contraction usage is most appropriate in describing this error to a non-technical stakeholder?
This scenario tests the ability to translate technical jargon into accessible language. 'Insufficient permissions' can be simplified without sacrificing accuracy. Using contractions like 'doesn't' or 'is failing' would overcomplicate the message and risk misunderstanding. The key is clear, concise communication tailored to the recipient's knowledge level.
11 / 16
Emily writes a technical blog post about container orchestration: 'Kubernetes is an amazing system. It's really easy to use and it simplifies deployments.' Which of the following statements accurately demonstrates the appropriate register for API reference documentation compared to this blog post?
Register shifts depending on the audience and purpose. Blog posts can afford a less formal style with simpler explanations, while API documentation demands precision and technical accuracy. Avoiding contractions and focusing on definitions are key to maintaining clarity and avoiding ambiguity in reference materials.
12 / 16
Mark is reviewing a pull request for a new image processing library. He sees this comment from David:
'We've updated the size calculation. It's gonna be faster now.'
Which of the following best describes Mark's response to this comment regarding contraction usage?
Mark is reviewing code, so a formal register is required. While contractions are common in everyday conversation, they aren't appropriate in professional code reviews where precision and clarity are paramount. Using 'gonna' introduces unnecessary informality and could be misinterpreted as a lack of attention to detail. The key here is recognizing the context – a critical review demands more polished language.
13 / 16
A support engineer receives this error message from a customer's application:
`{"status": "error", "message": "Invalid API key. Please verify your credentials."} `
Which of the following is the MOST appropriate response to include in a follow-up email?
This scenario requires a clear, direct, and professional tone. The API response itself is formal, so the follow-up message must mirror that register. Using contractions like 'gonna' would undermine the seriousness of the issue and suggest a lack of professionalism from the support engineer. The correct phrasing focuses on the problem and directs the user to take corrective action.
14 / 16
David sent this Slack message to the team: 'The server's down. It's a real mess.' Which of these options best describes David's use of language and why it might be problematic for IT communication? Consider register and appropriate contractions.
David's use of 'a real mess' isn't technically incorrect but leans towards informal language unsuitable for professional IT communication. While contractions like 'it's' are acceptable, the overall phrasing lacks the directness and precision expected in technical updates. Option 1 accurately identifies this issue.
15 / 16
Maria is drafting a pull request description for a change to the authentication module. She writes: 'We've fixed an issue where users couldn't log in. It's been resolved now.' Which option best reflects the most appropriate register and contraction usage for this scenario? Focus on clarity and professionalism.
Maria's original phrasing is too informal and uses contractions excessively. Option 0 provides a more formal and precise description of the change, using full sentences and avoiding colloquialisms. This demonstrates appropriate register for a PR description, ensuring clarity and professionalism.
16 / 16
Rajesh is giving a standup update: 'We've been working on the database optimization. It's looking good now.' Which of the following options best describes the most appropriate register and phrasing for this communication? Consider audience and message clarity
Rajesh's original statement is slightly vague and informal. Option 0 provides a more complete and professional update by explicitly stating that progress has been made ('we're making progress') and confirming the positive outcome ('it's looking good'). This demonstrates clear communication during a standup update.
What will I practise in "Contractions and Register in IT Communication — Grammar Exercise"?
Practise when to use contractions (don't, isn't, we've) vs full forms across Slack, error messages, code comments, PR descriptions, and documentation.
How many exercises are in this module?
This module has 16 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.