5 exercises — ensuring all bullet list items use the same grammatical form in READMEs, checklists, PR descriptions, and API docs.
0 / 20 completed
1 / 20
A README lists the features of a CLI tool. Which list has correct parallel structure?
Option D is correct — both B and C are parallel. Option B uses third-person singular present tense verbs throughout ("Authenticates, Rate-limits, Logs, Manages") — a common pattern for feature lists that describe what a tool does. Option C uses noun phrases throughout ("User authentication, Rate limiting, Automatic error logging, Cache management") — a common pattern for bullet-point feature summaries. Option A breaks parallel structure by mixing gerunds ("Authenticating", "Rate limiting"), an infinitive ("To log"), and a noun ("Cache management"). The rule: every item in a list must belong to the same grammatical category. Never mix verb phrases, noun phrases, and infinitives in the same list.
2 / 20
A deployment checklist contains these items. Which version has correct parallel structure?
Option B is the correct parallel structure. All four items use the same pattern: imperative verb + object (Run, Build, Push, Deploy). This is the standard structure for checklists, runbooks, and step-by-step guides — imperative verbs make each item an action the reader should perform. Option A mixes a complex clause ("Run all tests and they must pass"), an imperative ("Build"), a gerund ("Pushing"), and another imperative ("Deploy") — four different structures. Option C uses passive voice inconsistently and mixes passive with gerunds. Option D mixes gerunds ("Running", "Deploying") with noun phrases ("Image build") and an imperative ("Push"). Checklist rule: imperative verb + direct object, every item, every time.
3 / 20
An API reference lists what an endpoint returns. Which version is grammatically parallel?
Option B is the best for prose documentation — every item is a noun phrase starting with an article ("A", "An", "The", "An"): consistent grammatical category throughout. Option D is also parallel (all key-value pairs), and is actually the preferred format in API reference documentation — it is more compact and machine-readable. Both B and D are correct for their contexts; B for prose-style API docs, D for reference tables. Option A is broken: "A JSON object" (noun phrase), "It includes" (clause), "Status" (bare noun), "Errors are returned" (passive clause) — four different patterns. Option C mixes passive clauses, a clause, a bare noun, and a reduced clause. Key rule: choose noun phrases or key-value pairs for API returns — never mix in clauses.
4 / 20
A PR description lists the changes made. Which list is parallel?
Option D is correct — both B and C are parallel. Option B uses past tense verb phrases ("Added, Refactored, Updated, Fixed") — the standard for PR descriptions, which document what was done. Option C uses gerund noun phrases ("Null check addition, Config loader refactoring…") — concise noun phrases are used in commit messages and changelogs. Option A breaks parallel structure: "Added" (past tense), "Refactored" (past tense), "Tests have been updated" (passive clause — not a bullet phrase), "Fix" (present tense imperative). The rule for PR descriptions: use past tense verbs throughout ("Added", "Fixed", "Updated", "Removed") — they document completed actions. Changelog convention: noun phrases or past tense, consistently one or the other.
5 / 20
A microservices architecture document lists service responsibilities. Which list is parallel?
Option D is correct — both B and C use consistent grammatical patterns throughout. Option B uses third-person singular present verbs ("Validates, Authenticates, Issues, Rate-limits") — the standard for service capability descriptions in architecture documents. Option C uses gerund noun phrases ("JWT token validation, LDAP-based authentication…") after "is responsible for" — also a strong, consistent pattern. Both are correct for different contexts: B is better inline in prose; C is better after a setup phrase ("is responsible for"). Option A mixes verb ("Validates"), passive clause ("The user is authenticated"), gerund ("Issuing"), and noun ("Rate limiting") — four different patterns. Whenever you write a list describing what a system does, commit to one grammatical pattern before you start.
6 / 20
Sarah is reviewing a code change for the update_user function. The commit message reads: 'Fixes bugs related to user data validation and improves error handling.' Which of the following revisions best demonstrates parallel structure in this commit message, aligning with standard practice for technical documentation?
The key here is consistent phrasing. Using 'resolved errors' mirrors 'fixes bugs,' creating a parallel structure that clearly outlines the two actions taken. Option 2 provides this balance; the other options use different verb tenses and constructions, disrupting the flow and making it less clear what was accomplished.
7 / 20
During a Slack discussion about migrating to a new database schema, Alex writes: 'We need to migrate the data from MySQL to PostgreSQL and optimize queries for performance.' Which of the following statements best exemplifies parallel structure in this message, reflecting how technical requirements are typically presented?
Parallel structure requires a consistent grammatical form when listing related items. Alex's statement uses parallel verbs – 'migrate,' 'optimize' – creating a balanced list of actions. Option 0 maintains this balance effectively, ensuring clarity in the request.
8 / 20
You're drafting a PR description for adding support for JSON Web Tokens (JWT) to your authentication service. Which of the following descriptions demonstrates parallel structure and provides the most concise explanation to reviewers?
Parallel structure here means using similar grammatical constructions to describe related features. 'Implemented JWT support' is paired with 'token validation and user authentication,' creating a balanced and easily understandable description. Option 1 achieves this parallel construction effectively.
9 / 20
In a standup update, David says: 'I finished the backend API integration and implemented user authentication flows. I also addressed performance bottlenecks in the data access layer.' Which of these revisions best demonstrates parallel structure, suitable for a concise team update?
Parallel structure involves repeating a grammatical pattern. David's statement uses 'completed…implemented…tackled' to describe his tasks – a balanced list of actions that clearly communicates what he achieved during the standup. Option 0 maintains this parallel structure.
10 / 20
A technical document describes a new feature flag system. It states: 'The system allows developers to enable or disable features and provides detailed logging for debugging purposes.' Which of the following options demonstrates parallel structure in this section, aligning with best practices for technical documentation clarity?
Parallel structure in this context focuses on a consistent phrasing of capabilities. 'Enabling or disabling features' is paired with 'receive detailed logs,' presenting two distinct benefits of the feature flag system in a clear and balanced manner. Option 3 maintains this parallel relationship.
11 / 20
Sarah is reviewing a code change for the update_user function. The commit message reads: 'Fixes bugs related to user data validation and improves error handling.' Which of the following revisions best demonstrates parallel structure in this commit message, aligning with standard practice for technical documentation?
The key here is consistent phrasing. Using 'resolved errors' mirrors 'fixes bugs,' creating a parallel structure that clearly outlines the two actions taken. Option 2 provides this balance; the other options use different verb tenses and constructions, disrupting the flow and making it less clear what was accomplished.
12 / 20
During a Slack discussion about migrating to a new database schema, Alex writes: 'We need to migrate the data from MySQL to PostgreSQL and optimize queries for performance.' Which of the following statements best exemplifies parallel structure in this message, reflecting how technical requirements are typically presented?
Parallel structure requires a consistent grammatical form when listing related items. Alex's statement uses parallel verbs – 'migrate,' 'optimize' – creating a balanced list of actions. Option 0 maintains this balance effectively, ensuring clarity in the request.
13 / 20
You're drafting a PR description for adding support for JSON Web Tokens (JWT) to your authentication service. Which of the following descriptions demonstrates parallel structure and provides the most concise explanation to reviewers?
Parallel structure here means using similar grammatical constructions to describe related features. 'Implemented JWT support' is paired with 'token validation and user authentication,' creating a balanced and easily understandable description. Option 1 achieves this parallel construction effectively.
14 / 20
In a standup update, David says: 'I finished the backend API integration and implemented user authentication flows. I also addressed performance bottlenecks in the data access layer.' Which of these revisions best demonstrates parallel structure, suitable for a concise team update?
Parallel structure involves repeating a grammatical pattern. David's statement uses 'completed…implemented…tackled' to describe his tasks – a balanced list of actions that clearly communicates what he achieved during the standup. Option 0 maintains this parallel structure.
15 / 20
A technical document describes a new feature flag system. It states: 'The system allows developers to enable or disable features and provides detailed logging for debugging purposes.' Which of the following options demonstrates parallel structure in this section, aligning with best practices for technical documentation clarity?
Parallel structure in this context focuses on a consistent phrasing of capabilities. 'Enabling or disabling features' is paired with 'receive detailed logs,' presenting two distinct benefits of the feature flag system in a clear and balanced manner. Option 3 maintains this parallel relationship.
16 / 20
Sarah is reviewing a code change for the update_user function. The commit message reads: 'Fixes bugs related to user data validation and improves error handling.' Which of the following revisions best demonstrates parallel structure in this commit message, aligning with standard practice for technical documentation?
The key here is consistent phrasing. Using 'resolved errors' mirrors 'fixes bugs,' creating a parallel structure that clearly outlines the two actions taken. Option 2 provides this balance; the other options use different verb tenses and constructions, disrupting the flow and making it less clear what was accomplished.
17 / 20
During a Slack discussion about migrating to a new database schema, Alex writes: 'We need to migrate the data from MySQL to PostgreSQL and optimize queries for performance.' Which of the following statements best exemplifies parallel structure in this message, reflecting how technical requirements are typically presented?
Parallel structure requires a consistent grammatical form when listing related items. Alex's statement uses parallel verbs – 'migrate,' 'optimize' – creating a balanced list of actions. Option 0 maintains this balance effectively, ensuring clarity in the request.
18 / 20
You're drafting a PR description for adding support for JSON Web Tokens (JWT) to your authentication service. Which of the following descriptions demonstrates parallel structure and provides the most concise explanation to reviewers?
Parallel structure here means using similar grammatical constructions to describe related features. 'Implemented JWT support' is paired with 'token validation and user authentication,' creating a balanced and easily understandable description. Option 1 achieves this parallel construction effectively.
19 / 20
In a standup update, David says: 'I finished the backend API integration and implemented user authentication flows. I also addressed performance bottlenecks in the data access layer.' Which of these revisions best demonstrates parallel structure, suitable for a concise team update?
Parallel structure involves repeating a grammatical pattern. David's statement uses 'completed…implemented…tackled' to describe his tasks – a balanced list of actions that clearly communicates what he achieved during the standup. Option 0 maintains this parallel structure.
20 / 20
A technical document describes a new feature flag system. It states: 'The system allows developers to enable or disable features and provides detailed logging for debugging purposes.' Which of the following options demonstrates parallel structure in this section, aligning with best practices for technical documentation clarity?
Parallel structure in this context focuses on a consistent phrasing of capabilities. 'Enabling or disabling features' is paired with 'receive detailed logs,' presenting two distinct benefits of the feature flag system in a clear and balanced manner. Option 3 maintains this parallel relationship.
What will I practise in "Parallel Structure in Technical Lists — Grammar Exercise"?
Practice parallel structure in bullet lists: READMEs, checklists, PR descriptions, and API docs — all items as nouns or all as verb phrases.
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.