A tech lead asks you to rewrite this dense sentence for a junior developer audience: "The idempotent, asynchronous, rate-limited webhook dispatcher batches and retries failed delivery attempts using an exponential back-off strategy configurable via the WEBHOOK_RETRY_CONFIG environment variable." Which rewrite is best?
Option A is correct. The rewrite splits one overloaded sentence into three focused sentences, each carrying one main idea. This is the core principle of managing information density: one idea per sentence for foundational documentation aimed at a mixed audience. Option B strips out too much — idempotency and batching matter for debugging. Option C omits all context and leaves the reader with no mental model. Option D keeps all the same information in an even worse structure by stringing clauses with "and". Breaking dense sentences apart is the most reliable way to improve comprehension without losing technical accuracy.
2 / 20
Which sentence is appropriately dense for an API reference aimed at experienced developers?
Option B is correct. API reference documentation for experienced developers should be dense but precise: every word carries information. Option B packs the HTTP method, path, behaviour, status code, and key response field into one sentence — the right density for a reference table. Option A is vague and useless as a reference. Option C is a verbose prose rewrite that adds nothing but words — the opposite of a good API reference style. Option D is too telegraphic: it loses the behaviour description ("enqueues a background job") which is the most important piece. Density in API docs means: no padding, no missing semantics.
3 / 20
A senior engineer reviews a README section and writes: "This paragraph is trying to do too much." Which paragraph are they most likely commenting on?
Option C is the overloaded paragraph. It chains six distinct steps in a single sentence without numbering, headings, or line breaks. Each step (install, configure, migrate, seed, start, verify) deserves its own numbered list item. Dense prose works well for explanatory text but is harmful for procedural text — readers following instructions need to track their position, and a wall of steps in a single sentence makes that impossible. Options A, B, and D are appropriately simple single-idea sentences. The fix is not to compress but to restructure: use a numbered list, one imperative verb per item.
4 / 20
You are writing a Confluence architecture decision record (ADR). Which approach to information density is correct for the context and rationale section?
Option B is correct. Information density should be calibrated to audience and document type. An ADR is read by senior engineers and architects who need to understand the full reasoning chain — that requires connected prose with causal connectors, not fragmented bullets. Dense reasoning in an ADR is appropriate because the audience can handle it and the document's purpose is to preserve complex decision logic. Short sentences work for procedures and quick-reference docs. Bullet points break logical flow when reasoning is interconnected. The 30-word limit (Option D) would make the ADR useless as a decision record.
5 / 20
A developer writes this Slack message to the team: "Hey, so I was looking at the logs and I noticed that when the cron job runs at midnight it sometimes — not always but sometimes — fails with a timeout error which I think might be because the DB connection pool gets exhausted but I'm not 100% sure, maybe someone with more DB experience could look at it?" Which rewrite has the ideal information density for a team Slack channel?
Option B is correct. Slack messages aimed at triggering action need high signal density with low noise: state the problem, the hypothesis, the ask, and include the evidence (link to logs). Option B achieves all four in 20 words plus a placeholder for the link. Option A is too compressed — "DB maybe" loses the mechanism hypothesis and the action request. Option C is over-formal for Slack and buries the ask at the end. Option D keeps all the hedging from the original and adds no clarity. In asynchronous team communication, density means: no filler words, but all essential facts present.
6 / 20
Code Review Context: During a code review of a new API endpoint, Liam comments on Sarah's PR:
'This response is incredibly verbose. It includes details about the user's session expiry and IP address that aren't relevant to the core operation – retrieving product data. Can we simplify this?'
Which phrasing best reflects Liam's concern regarding information density in this scenario?
Liam's comment highlights unnecessary detail. Information density in code reviews focuses on relevance – data included should directly support the immediate purpose of the endpoint. Option A misinterprets Liam's feedback by praising excessive detail. Option C suggests a different problem (error codes) and option D advocates for inconsistency, both irrelevant to the core concern about reducing verbosity.
7 / 20
Slack Message Context: Mark sends this message in a Slack channel discussing performance issues with a microservice:
'The service is experiencing high latency. Initial investigations point to slow database queries and excessive network calls. We're monitoring CPU usage, which appears normal.'
Which sentence best demonstrates an appropriate level of information density for this Slack message?
Option 1 provides a concise summary of the observed symptoms (high latency) and suggests immediate investigation steps. It avoids speculation or overly dramatic language. Option A is too reactive; option C focuses on solutions without summarizing the problem, and option D repeats information already stated but doesn't contribute to understanding.
8 / 20
PR Description Context: You're writing the description for a PR that implements a new feature – a rate limiter. The description is currently:
'This change introduces a new rate limiting mechanism to prevent abuse of the API endpoint. It uses a token bucket algorithm and allows up to 100 requests per minute.'
Which revision best improves the information density for a PR description?
Option 0 provides a clear and concise explanation of the implemented solution. It uses precise terminology (token bucket algorithm) and quantifies the limit (100 requests per minute). Option A is repetitive; option C is too verbose and abstract, and option D lacks technical detail and is overly enthusiastic.
9 / 20
Standup Update Context: During a daily standup, David says:
'I'm working on improving the performance of the user authentication service. I've been profiling the code and identified some areas where we can optimize.'
Which statement best exemplifies information density in this stand-up update?
Option 1 provides specific details about David's activity (investigating bottlenecks) and his planned next steps (sharing findings). This demonstrates a focused update that conveys relevant information efficiently. Options A and B are vague; option C focuses on time spent rather than progress, and option D is a non-update.
10 / 20
API Response Context: You're designing an API response for retrieving customer order information. The current response includes all historical order data, regardless of whether it's relevant to the current request. Which approach best demonstrates information density in this scenario?
Filtering the response to include only relevant data is the most effective way to manage information density. This reduces the size and complexity of the response, improving performance and making it easier for clients to process the data efficiently. Option A prioritizes completeness over efficiency; option C offers no control over relevance; and option D introduces pagination which isn't directly addressing the core issue of information density within a single response.
11 / 20
Code Review Context: During a code review of a new API endpoint, Liam comments on Sarah's PR:
'This response is incredibly verbose. It includes details about the user's session expiry and IP address that aren't relevant to the core operation – retrieving product data. Can we simplify this?'
Which phrasing best reflects Liam's concern regarding information density in this scenario?
Liam's comment highlights unnecessary detail. Information density in code reviews focuses on relevance – data included should directly support the immediate purpose of the endpoint. Option A misinterprets Liam's feedback by praising excessive detail. Option C suggests a different problem (error codes) and option D advocates for inconsistency, both irrelevant to the core concern about reducing verbosity.
12 / 20
Slack Message Context: Mark sends this message in a Slack channel discussing performance issues with a microservice:
'The service is experiencing high latency. Initial investigations point to slow database queries and excessive network calls. We're monitoring CPU usage, which appears normal.'
Which sentence best demonstrates an appropriate level of information density for this Slack message?
Option 1 provides a concise summary of the observed symptoms (high latency) and suggests immediate investigation steps. It avoids speculation or overly dramatic language. Option A is too reactive; option C focuses on solutions without summarizing the problem, and option D repeats information already stated but doesn't contribute to understanding.
13 / 20
PR Description Context: You're writing the description for a PR that implements a new feature – a rate limiter. The description is currently:
'This change introduces a new rate limiting mechanism to prevent abuse of the API endpoint. It uses a token bucket algorithm and allows up to 100 requests per minute.'
Which revision best improves the information density for a PR description?
Option 0 provides a clear and concise explanation of the implemented solution. It uses precise terminology (token bucket algorithm) and quantifies the limit (100 requests per minute). Option A is repetitive; option C is too verbose and abstract, and option D lacks technical detail and is overly enthusiastic.
14 / 20
Standup Update Context: During a daily standup, David says:
'I'm working on improving the performance of the user authentication service. I've been profiling the code and identified some areas where we can optimize.'
Which statement best exemplifies information density in this stand-up update?
Option 1 provides specific details about David's activity (investigating bottlenecks) and his planned next steps (sharing findings). This demonstrates a focused update that conveys relevant information efficiently. Options A and B are vague; option C focuses on time spent rather than progress, and option D is a non-update.
15 / 20
API Response Context: You're designing an API response for retrieving customer order information. The current response includes all historical order data, regardless of whether it's relevant to the current request. Which approach best demonstrates information density in this scenario?
Filtering the response to include only relevant data is the most effective way to manage information density. This reduces the size and complexity of the response, improving performance and making it easier for clients to process the data efficiently. Option A prioritizes completeness over efficiency; option C offers no control over relevance; and option D introduces pagination which isn't directly addressing the core issue of information density within a single response.
16 / 20
Code Review Context: During a code review of a new API endpoint, Liam comments on Sarah's PR:
'This response is incredibly verbose. It includes details about the user's session expiry and IP address that aren't relevant to the core operation – retrieving product data. Can we simplify this?'
Which phrasing best reflects Liam's concern regarding information density in this scenario?
Liam's comment highlights unnecessary detail. Information density in code reviews focuses on relevance – data included should directly support the immediate purpose of the endpoint. Option A misinterprets Liam's feedback by praising excessive detail. Option C suggests a different problem (error codes) and option D advocates for inconsistency, both irrelevant to the core concern about reducing verbosity.
17 / 20
Slack Message Context: Mark sends this message in a Slack channel discussing performance issues with a microservice:
'The service is experiencing high latency. Initial investigations point to slow database queries and excessive network calls. We're monitoring CPU usage, which appears normal.'
Which sentence best demonstrates an appropriate level of information density for this Slack message?
Option 1 provides a concise summary of the observed symptoms (high latency) and suggests immediate investigation steps. It avoids speculation or overly dramatic language. Option A is too reactive; option C focuses on solutions without summarizing the problem, and option D repeats information already stated but doesn't contribute to understanding.
18 / 20
PR Description Context: You're writing the description for a PR that implements a new feature – a rate limiter. The description is currently:
'This change introduces a new rate limiting mechanism to prevent abuse of the API endpoint. It uses a token bucket algorithm and allows up to 100 requests per minute.'
Which revision best improves the information density for a PR description?
Option 0 provides a clear and concise explanation of the implemented solution. It uses precise terminology (token bucket algorithm) and quantifies the limit (100 requests per minute). Option A is repetitive; option C is too verbose and abstract, and option D lacks technical detail and is overly enthusiastic.
19 / 20
Standup Update Context: During a daily standup, David says:
'I'm working on improving the performance of the user authentication service. I've been profiling the code and identified some areas where we can optimize.'
Which statement best exemplifies information density in this stand-up update?
Option 1 provides specific details about David's activity (investigating bottlenecks) and his planned next steps (sharing findings). This demonstrates a focused update that conveys relevant information efficiently. Options A and B are vague; option C focuses on time spent rather than progress, and option D is a non-update.
20 / 20
API Response Context: You're designing an API response for retrieving customer order information. The current response includes all historical order data, regardless of whether it's relevant to the current request. Which approach best demonstrates information density in this scenario?
Filtering the response to include only relevant data is the most effective way to manage information density. This reduces the size and complexity of the response, improving performance and making it easier for clients to process the data efficiently. Option A prioritizes completeness over efficiency; option C offers no control over relevance; and option D introduces pagination which isn't directly addressing the core issue of information density within a single response.
What will I practise in "Information Density in Technical Writing — Grammar Exercise"?
Practice calibrating how much information to pack into a sentence for different technical audiences and document types.
How many exercises are in this module?
This module has 20 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.