5 exercises — introduce on first use, plural forms, possessives, a vs an before acronyms, and avoiding acronym soup.
0 / 13 completed
1 / 13
A technical document introduces an abbreviation. Which sentence follows the correct convention?
Option D is correct — both B and C follow the standard convention. The rule is: spell out the full term first, then place the abbreviation in parentheses: "Command-Line Interface (CLI)". After that, use "CLI" alone throughout the document. Option A reverses this — it introduces the abbreviation before the full term, which is incorrect. Some style guides (Google Developer Style, Microsoft) accept either order as long as the pattern is consistent, but the "full term first" convention is universal across technical documentation. Never introduce an abbreviation and then never use it — if you only mention it once, spell it out without abbreviating.
2 / 13
Which sentence correctly forms the plural of an abbreviation?
Option B is correct. The plural of an abbreviation is formed by adding a lowercase "s" directly — no apostrophe. "APIs", "CRDs", "VMs", "READMEs". Option A uses an apostrophe ("API's") — this is the possessive form, not the plural. "API's response time is…" (possessive) vs "three APIs" (plural). Option C lowercases the acronym — abbreviations should maintain their original casing. Option D uses mixed case ("APis") which is incorrect. Common plurals: APIs, CLIs, VPCs, CRDs, SLAs, ADRs, PRs, VMs. Memory aid: apostrophe = possession; s alone = plural.
3 / 13
A README section references multiple abbreviations in sequence. Which version is clearest?
Option B is the strongest. It introduces the key abbreviation explicitly ("Infrastructure as Code (IaC)"), uses an em-dash interruption to name the specific tool (AWS CDK), and expands vendor-specific product names on first mention (Amazon ECS, Amazon ECR). Chaining multiple unexplained abbreviations — as in Option A — creates an "acronym soup" that is opaque to readers unfamiliar with the full stack. Option C removes the slash from CI/CD (incorrect) and capitalises IaC as IAC. Option D spells out every abbreviation — fine for a glossary but painful to read in a README. The rule for abbreviation chains: expand the least-known ones, keep the universally known ones (CI/CD, IAM) abbreviated.
4 / 13
Which sentence uses the possessive of an abbreviation correctly?
Option D is correct. Option B is the correct possessive form for a singular noun: "API's rate limit" (the rate limit belonging to the API). The apostrophe-s construction is standard for abbreviation possessives. Option C is also commonly preferred in technical writing — many style guides (Google Developer Style in particular) recommend avoiding possessives with product names and abbreviations by restructuring: "API rate limit" (noun modifier) instead of "API's rate limit". Option A ("APIs'" with apostrophe after the s) would be correct for a plural possessive: "the APIs' combined throughput" (the throughput of multiple APIs). Both B and C are widely used; know both patterns.
5 / 13
An article vs abbreviation question: which is correct — "a API" or "an API"?
Option B is correct. The rule for articles before abbreviations depends on pronunciation, not spelling. "API" is pronounced "ay-pee-eye" — the first sound is the vowel "ay". Therefore: "an API", "an SLA", "an RFC", "an HTTP request", "an SQL query". For abbreviations pronounced as words (acronyms): "a URL" (you-ar-el, starts with consonant "you") → actually pronounced "earl" by some, but "you" is the standard → use "a URL". Common patterns: an API, an SLA, an ADR, an IDE, an ORM, an ETL pipeline. Contrast: a CI/CD pipeline (pronounced "see-eye-see-dee" — "see" starts with consonant sound), a REST API (pronounced "rest").
6 / 13
Reviewer: 'The server returned a 500 status code. Investigate the error logs and look for potential issues with the API call.'
You: 'Can you clarify what 'API call' refers to? Is it a specific endpoint or something else?'
The original phrasing of the reviewer's question could be confusing for a non-native speaker. While 'API call' is common in development, simply stating it needs clarification is not sufficient; it requires more detail to ensure understanding. The best response acknowledges the need for context without repeating jargon unnecessarily – this demonstrates an intermediate level of English proficiency and proactive problem-solving. Adding that the phrase refers to a specific endpoint would be ideal.
7 / 13
Sarah: 'The team needs to triage these incoming tickets. We're seeing a lot of errors related to the JWT validation failing.'
David (responding in an internal Slack channel) wants to understand what Sarah means. Which of the following responses would be most appropriate and professional for David to send?
The key here is David's role as a peer seeking clarification. Option 1 demonstrates a lack of engagement and doesn't address Sarah's statement. Option 2 is the best approach – it politely asks for elaboration on the technical term JWT (which is commonly used in authentication) and specifically identifies the problem area, prompting Sarah to provide more details. Options 3 and 4 are too reactive or offer unhelpful assistance without understanding the context.
8 / 13
Reviewer: 'The server returned a 500 status code. Investigate the error logs and look for potential issues with the API call.'
You: 'Can you clarify what 'API call' refers to? Is it a specific endpoint or something else?'
The original phrasing of the reviewer's question could be confusing for a non-native speaker. While 'API call' is common in development, simply stating it needs clarification is not sufficient; it requires more detail to ensure understanding. The best response acknowledges the need for context without repeating jargon unnecessarily – this demonstrates an intermediate level of English proficiency and proactive problem-solving. Adding that the phrase refers to a specific endpoint would be ideal.
9 / 13
Sarah: 'The team needs to triage these incoming tickets. We're seeing a lot of errors related to the JWT validation failing.'
David (responding in an internal Slack channel) wants to understand what Sarah means. Which of the following responses would be most appropriate and professional for David to send?
The key here is David's role as a peer seeking clarification. Option 1 demonstrates a lack of engagement and doesn't address Sarah's statement. Option 2 is the best approach – it politely asks for elaboration on the technical term JWT (which is commonly used in authentication) and specifically identifies the problem area, prompting Sarah to provide more details. Options 3 and 4 are too reactive or offer unhelpful assistance without understanding the context.
10 / 13
Reviewer: 'The server returned a 500 status code. Investigate the error logs and look for potential issues with the API call.'
You: 'Can you clarify what 'API call' refers to? Is it a specific endpoint or something else?'
The original phrasing of the reviewer's question could be confusing for a non-native speaker. While 'API call' is common in development, simply stating it needs clarification is not sufficient; it requires more detail to ensure understanding. The best response acknowledges the need for context without repeating jargon unnecessarily – this demonstrates an intermediate level of English proficiency and proactive problem-solving. Adding that the phrase refers to a specific endpoint would be ideal.
11 / 13
Sarah: 'The team needs to triage these incoming tickets. We're seeing a lot of errors related to the JWT validation failing.'
David (responding in an internal Slack channel) wants to understand what Sarah means. Which of the following responses would be most appropriate and professional for David to send?
The key here is David's role as a peer seeking clarification. Option 1 demonstrates a lack of engagement and doesn't address Sarah's statement. Option 2 is the best approach – it politely asks for elaboration on the technical term JWT (which is commonly used in authentication) and specifically identifies the problem area, prompting Sarah to provide more details. Options 3 and 4 are too reactive or offer unhelpful assistance without understanding the context.
12 / 13
A software engineer is writing a comment for a unit test. Which of the following best describes how to use the abbreviation 'UI' in this context?
Using abbreviations within code comments should be done with extreme caution. 'UI' here refers to User Interface testing and needs definition for clarity. Options B and C are incorrect because they provide insufficient context and introduce potential ambiguity.
13 / 13
PR Description: 'The build failed due to an error in the payment gateway integration. The service returned a 400 status code and the response body indicated invalid credentials.'
Which of the following is the MOST appropriate way to shorten 'response body indicated invalid credentials' for clarity within this PR description?
This question examines the balance between brevity and clarity when using abbreviations. While 'invalid credentials' is a valid abbreviation, it's acceptable in this context due to its frequent use within the described scenario. Option 3 is overly formal, and option 4 suggests an inappropriate tone for professional documentation.
What will I practise in "Abbreviations in Technical Writing — Grammar Exercise"?
Practice correct abbreviation usage in technical writing: introduce on first use, plural forms, possessives, articles (a vs an), and acronym chains.
How many exercises are in this module?
This module has 13 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.