5 exercises — given-new structure, fronting, end-weight, and sentence rhythm in technical docs and error messages.
0 / 17 completed
1 / 17
Which sentence places the most important information in the most emphatic position?
Option C uses fronting ("During the outage") to provide given context first, then places "47 minutes of transaction data was lost" in the main clause — the most emphatic position. End-weight principle: new, important, or quantified information should appear at or near the end of the clause. Option B is also good but omits the temporal context. The given-new principle: readers process sentences by anchoring to known information (the outage) before receiving new information (47 minutes lost).
2 / 17
A developer is writing an error message. Which version most clearly signals what went wrong and what to do?
Option C follows the optimal word order for error messages: [error type]: [what happened] + [action]. The key information (what failed: connection timeout; how long: 30 seconds; what to do: retry or check) is structured in given-new order. Technical writing style guides (Google, Microsoft) consistently recommend: label first, description second, action last.
3 / 17
Reorder this poorly structured sentence: "The fact that the queue was not drained before the deployment was the root cause of the data loss." Choose the clearer version:
Option A applies end-weight by moving the cause ("not draining the queue before deployment") to the end as a prepositional phrase, keeping the sentence tight. It eliminates the "the fact that" nominalisation — a major source of unnecessary wordiness in technical writing. Option D is also clear and uses chronological order effectively, but option A is more concise. Prefer active constructions and direct cause-effect ordering.
4 / 17
Which sentence uses fronting most effectively for emphasis in a change log?
Option B fronts the temporal frame ("In the next major release") — the most important information for developers reading change logs (when will this happen?). The passive "will be removed" places the endpoints (what developers care about) in subject position. Fronting time adverbials in change logs and release notes is a standard convention: "In version 4.0...", "From January 2025...", "After migration...".
5 / 17
An engineer is writing the first sentence of an architecture decision record. Which opening best follows given-new and end-weight principles?
Option C applies given-new (sets context with "After evaluating..."), uses active voice ("the team selected"), and places the new information — the key decision details (PostgreSQL + its specific strengths: ACID compliance, JSON support) — at the end of the sentence. This structure maximises comprehension because readers know the decision context before receiving the verdict, and the rationale is attached to the decision it justifies.
6 / 17
David is writing a pull request description for a database schema change.
Which of the following descriptions most effectively uses word order to emphasize the *impact* of the change?
Starting with 'This update significantly improves…' immediately emphasizes the benefit – performance. Placing the most impactful information first is crucial for PR descriptions. Options A and B are too passive, while options C and D focus on *what* was done rather than *why* it matters to the user.
7 / 17
Emily is reviewing a colleague's code snippet:
```javascript
if (user.roles === 'admin') {
// Do admin actions
} else {
// Do standard user actions
}
```
Which of the following comments best uses word order to highlight a potential security vulnerability?
Framing the comment as a direct instruction – 'Check if `user.roles === 'admin'`…' – is more actionable and emphasizes the specific area requiring attention. The other options are too general or simply restate what the code does without highlighting the potential problem. This approach aligns with best practices for code review.
8 / 17
John is writing a Slack message to announce a new feature release:
'We've released version 2.0! This includes improved performance and a redesigned UI.'
Which revision best uses word order for emphasis?
Starting with 'Improved performance and a redesigned UI are included…' directly highlights the key benefits of the release. This is more impactful than simply announcing the version number or stating that it's released. Option A provides a clear and concise statement of value.
9 / 17
Mark is drafting a Slack message to his team regarding a performance bottleneck. Which phrasing best uses word order for emphasis?
'We're investigating a slowdown in the data processing pipeline.' vs. 'A slowdown has been observed in the data processing pipeline, and we're investigating it.'
Placing 'A slowdown has been observed...' at the beginning immediately draws attention to the problem itself. The other options present the investigation as secondary information, weakening the emphasis on the actual issue.
10 / 17
Maria is writing a standup update. Which statement effectively uses word order to emphasize the *delay* in resolving a critical issue?
'We're still working on resolving the database connection problem.' vs. 'The database connection problem is still unresolved, and we are continuing our efforts.'
By stating 'We're still working…', the emphasis falls squarely on the *ongoing* nature of the problem. This subtly conveys a sense of urgency and potential delay, which is crucial for standup updates.
11 / 17
David is reviewing a colleague's code:
function calculateTotal(items) {
let total = 0;
for (let i = 0; i < items.length; i++) {
total += items[i].price;
}
return total; // Incorrect: Doesn't handle null prices
}
Which of the following comments best uses word order to highlight the *critical omission*?
'The function calculates the total price of items.' vs. 'The function does not calculate the total price of items if any item's price is null.'
Clearly stating the *function's action* – 'calculates the total price' – is the standard approach. However, to emphasize the *missing functionality*, the alternative phrasing directly states what the function *doesn't* do in a more forceful manner.
12 / 17
Sarah is writing a code review comment on a colleague's commit:
```javascript
const result = someFunction(data);
```
Which of the following comments most effectively draws attention to a potential issue using word order?
'The function is called with data.' vs. 'Calling the function with data…'
The key here is fronting. Placing 'Calling the function with data' at the beginning immediately highlights the action and its subject. Option A simply restates what's happening without emphasis. Options C and D are too passive and don't draw attention to the *potential* problem – that the data might be incorrect or unexpected.
13 / 17
Mark is drafting a Slack message about a bug fix:
'We fixed a crash in the payment processing module. The issue was caused by an incorrect validation check.'
Which revision best uses word order to emphasize the *severity* of the problem?
'We fixed a crash…' vs. 'A crash… We fixed it.'
Starting with 'A crash…' immediately establishes the urgency and impact. Option B is also effective due to its placement. Options C simply describes what happened, while option D is too vague for emphasizing severity.
14 / 17
Alex is writing a pull request description for a new API endpoint. He wants to emphasize the key benefit of this change:
'This PR introduces a new endpoint for retrieving user profiles. The endpoint accepts a user ID as input and returns a JSON object containing the user's information.'
Which revision best uses word order to highlight the *primary purpose* of the endpoint?
The correct answer places the *benefit* (retrieving user profiles) at the beginning of the sentence, immediately drawing attention to its purpose. Options A and B are too descriptive; C prioritizes the action, and D is overly verbose. Fronting emphasizes key information.
15 / 17
Ben needs to explain a critical bug he discovered during testing of a new microservice. He's writing a Slack message to his team:
'The service is experiencing intermittent errors. The root cause appears to be related to the asynchronous data synchronization process.'
Which revision best uses word order for emphasis, highlighting the *severity* of the issue?
Starting with 'Intermittent errors are being experienced...' immediately draws attention to the problem's nature and severity. Option A is too passive. Option C shifts the focus to the cause, while option D suggests a need for investigation without emphasizing the immediate concern.
16 / 17
Chloe is writing a code review comment on a colleague's JavaScript function:
```javascript
const calculateArea = (width, height) => {
return width * height;
};```
Which of the following comments best uses word order to highlight the *potential for incorrect input*?
Placing 'It's important to ensure…' at the beginning directly addresses a potential problem – incorrect input. Options A and B are purely descriptive. Option D is too neutral, while option 2 focuses on describing how it works instead of identifying the risk.
17 / 17
David is writing a pull request description for a database schema change. Which of the following descriptions most effectively uses word order to emphasize the *impact* of the change?
Option A: 'This PR updates the user table with new columns for email and phone number.'
Option B: 'The user table has been updated to include email and phone number fields, enabling improved contact management.'
Option C: 'We've added a few columns to the user table. It's pretty simple.'
Option D: 'This PR modifies the schema of the user table, adding new fields for email and phone numbers.'
Option B is the best choice because it clearly states the *impact* of the change—'improved contact management'. The phrasing highlights why the update matters to other developers and stakeholders. Options A and D are too neutral; Option C lacks formality appropriate for a PR description.
What will I practise in "Word Order and Emphasis in Technical Writing — Grammar Exercise"?
Practice English sentence structure and information focus for clear, emphatic technical documentation.
How many exercises are in this module?
This module has 17 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.