5 exercises — practise parallelism in numbered steps, lists, comparisons, requirements, and JSDoc to write clear, consistent technical content.
0 / 15 completed
1 / 15
Which set of deployment steps follows correct parallel structure?
Parallel structure in numbered steps requires all items to share the same grammatical form. Option B is correct: all three steps use the base imperative form ("Run", "Push", "Update") — consistent and scannable. Option A mixes a gerund ("Running") with imperatives ("Push", "Update"). Option C mixes an imperative, a passive sentence, and a gerund. Option D mixes an imperative, a gerund, and a modal sentence. Technical style guides (Google, Microsoft, Apple) universally mandate imperative verb phrases for instructional steps: "Run", "Open", "Click", "Configure".
2 / 15
Which sentence contains a parallelism error in a technical comparison?
Option B has a parallelism error: it mixes three different grammatical structures after the linking verb "is": an adjective ("fast"), a verb phrase ("scales well"), and an adjective clause ("it is reliable"). All items in a parallel list must share the same grammatical category. Options A, C, and D all maintain parallelism: A uses three adjectives, C uses three nouns, D uses three comparative adjective phrases. In technical writing, parallelism is especially important in comparison tables, feature lists, and performance descriptions.
3 / 15
Which bullet-point list uses parallel noun phrases correctly?
Option B is correct: all four bullets are parallel noun phrases ("A new authentication module", "Performance improvements to the query engine", "A fix for the session timeout bug", "Enhanced logging"). Option A breaks parallelism by switching to full sentences ("We fixed…", "Logging has been enhanced") after noun phrases. Option C mixes participial phrases with a full sentence. Option D mixes gerunds with an infinitive. For release notes and changelogs, noun-phrase bullets are standard: they are concise, scannable, and easy to translate.
4 / 15
Which sentence correctly expresses parallel requirements in a technical specification?
Option B is correct: the modal "must" governs three parallel infinitive phrases — "encrypt all data at rest", "encrypt all data in transit", and "retain audit logs for 90 days". The shared auxiliary "must" applies to all three, and each phrase uses the same base verb form. Option A mixes a modal-verb construction ("must encrypt") with a passive clause ("should be encrypted") and another modal ("must be retained") — three different structures. Option C uses progressive forms ("be encrypting") incorrectly with "must" in requirements. Option D uses semicolons after the first clause then gerunds — structurally incorrect.
5 / 15
A developer is writing JSDoc for a function. Which parameter description list is correctly parallel?
Option B is the best parallel JSDoc style: each description starts with "The" + noun phrase, providing consistent syntactic structure — "The user's unique identifier", "The number of milliseconds to wait before timing out", "Whether to retry the request on failure". This pattern is recommended by JSDoc style guides. Option A is close but mixes "The" noun phrases with conditional clauses ("How long to wait", "If the request should be retried"). Option C is too terse and inconsistent. Option D varies structure between a bare noun ("User ID string value"), a full sentence ("It specifies…"), and a relative clause ("This is used to indicate…").
6 / 15
Sarah, during a code review of the new authentication service, commented: 'We need to ensure the API endpoints are secured with HTTPS and rate limiting. Also, we must implement strong password policies.' Which of the following revisions demonstrates the best parallel structure for her feedback?
The key to parallel structure here is consistency in phrasing. Option 1 uses a consistent 'and' construction with the actions being taken. Options 2 and 3 incorrectly switch between phrases starting with 'we need to' and other sentence structures, disrupting the flow and clarity of the feedback. Option 4's phrasing is overly verbose and doesn't maintain a parallel structure effectively.
7 / 15
David sends this Slack message to his team after discovering a performance bottleneck in the database query: 'The system is slow. We need to optimize the queries and reduce the load on the server. Furthermore, we should monitor these metrics.' Which sentence demonstrates correct parallel structure for David's message?
Parallel structure in this context means using a similar grammatical form for each element of a list. Option 0 correctly uses 'and' to connect the actions David wants his team to take. Options 1 and 2 incorrectly use conjunctions like 'while' or omit necessary words, breaking the parallel pattern. Option 3 is unnecessarily complex and doesn't maintain the required parallelism.
8 / 15
Maria is writing a PR description for a new feature that adds support for multiple languages. Which of the following descriptions best utilizes parallel structure?
Parallel structure here involves presenting related items in a consistent grammatical form. Option 1 uses parallel verb phrases – 'supporting…', 'generating…', 'handling…' – which creates a clear and concise description. Options 2 and 3 incorrectly use different sentence structures for each element. Option 4 is overly verbose and doesn't maintain parallelism effectively.
9 / 15
Ben needs to document a new API endpoint. Which of the following parameter descriptions demonstrates correct parallel structure?
Parallel structure in API documentation focuses on presenting parameter details consistently. Option 0 uses a standard format: '[parameter name]: [data type]', '[parameter name]: [description]'. This is the most readable and maintainable approach. Options 1 and 2 are less structured, while option 3 incorrectly uses inline data types without descriptive text.
10 / 15
Chloe is writing a technical specification for a new logging system. Which of the following statements demonstrates the most effective use of parallel structure?
Parallel structure here should describe the core functionalities of the logging system in a consistent way. Option 0 presents these three actions as a list using parallel verb phrases – 'record', 'provide', 'generate'. This creates a clear and concise description of the system's capabilities. Options 1 and 2 are awkwardly phrased, while option 3 is overly complex and loses the parallelism.
11 / 15
Sarah, during a code review of the new authentication service, commented: 'We need to ensure the API endpoints are secured with HTTPS and rate limiting. Also, we must implement strong password policies.' Which of the following revisions demonstrates the best parallel structure for her feedback?
The key to parallel structure here is consistency in phrasing. Option 1 uses a consistent 'and' construction with the actions being taken. Options 2 and 3 incorrectly switch between phrases starting with 'we need to' and other sentence structures, disrupting the flow and clarity of the feedback. Option 4's phrasing is overly verbose and doesn't maintain a parallel structure effectively.
12 / 15
David sends this Slack message to his team after discovering a performance bottleneck in the database query: 'The system is slow. We need to optimize the queries and reduce the load on the server. Furthermore, we should monitor these metrics.' Which sentence demonstrates correct parallel structure for David's message?
Parallel structure in this context means using a similar grammatical form for each element of a list. Option 0 correctly uses 'and' to connect the actions David wants his team to take. Options 1 and 2 incorrectly use conjunctions like 'while' or omit necessary words, breaking the parallel pattern. Option 3 is unnecessarily complex and doesn't maintain the required parallelism.
13 / 15
Maria is writing a PR description for a new feature that adds support for multiple languages. Which of the following descriptions best utilizes parallel structure?
Parallel structure here involves presenting related items in a consistent grammatical form. Option 1 uses parallel verb phrases – 'supporting…', 'generating…', 'handling…' – which creates a clear and concise description. Options 2 and 3 incorrectly use different sentence structures for each element. Option 4 is overly verbose and doesn't maintain parallelism effectively.
14 / 15
Ben needs to document a new API endpoint. Which of the following parameter descriptions demonstrates correct parallel structure?
Parallel structure in API documentation focuses on presenting parameter details consistently. Option 0 uses a standard format: '[parameter name]: [data type]', '[parameter name]: [description]'. This is the most readable and maintainable approach. Options 1 and 2 are less structured, while option 3 incorrectly uses inline data types without descriptive text.
15 / 15
Chloe is writing a technical specification for a new logging system. Which of the following statements demonstrates the most effective use of parallel structure?
Parallel structure here should describe the core functionalities of the logging system in a consistent way. Option 0 presents these three actions as a list using parallel verb phrases – 'record', 'provide', 'generate'. This creates a clear and concise description of the system's capabilities. Options 1 and 2 are awkwardly phrased, while option 3 is overly complex and loses the parallelism.
What will I practise in "Parallel Structure in Technical Writing — IT English Grammar Exercise"?
Practise parallel structure in technical documentation: instruction steps, comparison sentences, bullet-point lists, requirements, and API documentation.
How many exercises are in this module?
This module has 15 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.