5 exercises — practise colons, semicolons, em-dashes, the Oxford comma, and hyphens in technical documentation and IT communication.
0 / 27 completed
1 / 27
Which sentence correctly uses a colon before a list in technical documentation?
A colon before a list requires a grammatically complete clause before it. Option B is correct: "The API supports the following methods" is a complete sentence. Option A is wrong because "supports:" interrupts the verb-object relationship — the colon splits the verb from its object. Option D has the same problem: "are:" splits the linking verb from its complement. Use "the following" or "as follows" to create a complete introductory clause.
2 / 27
Which sentence best uses a semicolon to join two related independent clauses in a technical context?
Option A correctly uses a semicolon with a conjunctive adverb ("however") to connect two complete independent clauses — each side can stand alone as a sentence. Option B uses "but" after a semicolon, which is incorrect; coordinating conjunctions (but, and, or) follow a comma, not a semicolon. Option C has a fragment after the semicolon ("tests failing in staging" is not a complete clause). Option D uses a semicolon before an infinitive phrase, which is wrong.
3 / 27
A tech writer is adding an aside to a sentence in a PR description. Which version uses punctuation most appropriately?
All three options are grammatically correct; the difference is rhetorical. Em-dashes (—) create the strongest interruption and add emphasis — suitable when the aside is dramatic or pivotal. Commas create the lightest, most neutral pause — standard for non-restrictive relative clauses. Parentheses (round brackets) signal the information is supplementary or technical detail the reader may skip. In PR descriptions and documentation, all three forms are acceptable; choose based on how prominently you want to feature the aside.
4 / 27
Which sentence correctly applies the serial (Oxford) comma in a technical context?
The serial comma (before the final "and" in a list) is strongly recommended in technical writing because it prevents ambiguity. Compare: "The services are authentication, logging and error handling" — does "logging and error handling" form a single combined service or two separate ones? The Oxford comma removes that ambiguity: "authentication, logging, and error handling" clearly lists three independent items. Option C incorrectly uses a colon after "requires". Option D uses semicolons, which are reserved for lists where the items themselves contain commas.
5 / 27
Which phrase correctly hyphenates a compound adjective before a noun in technical writing?
Compound adjectives before a noun are hyphenated: "real-time" and "data-processing" each function as single pre-modifying units, so both are hyphenated when placed before "system". Without hyphens, "real time data processing system" is a five-noun stack with no visual grouping — ambiguous and hard to parse. "Realtime" as one word is sometimes seen in informal developer writing but is not standard in technical documentation. Rule: hyphenate compound adjectives before the noun; drop hyphens after a linking verb ("the processing is real time").
6 / 27
Context: During a code review of the payment_processing.py module, Liam comments on Sarah's use of a conditional statement. Which option demonstrates the most appropriate punctuation for this comment?
The correct answer uses a semicolon to separate the two parts of the conditional statement, adhering to standard Python syntax. The other options incorrectly use either a colon or question mark in this context, which would be inappropriate for a code review comment. It's crucial to maintain clarity and accuracy when describing code logic.
7 / 27
Context: You're drafting the description for a Pull Request introducing a new API endpoint. Which of the following options best uses punctuation to clearly define the endpoint's purpose?
The correct answer clearly defines the endpoint's URL and its intended function using a descriptive phrase. The other options are too brief or include unnecessary details like query parameters – PR descriptions should focus on *what* the change does, not *how* it's implemented. Using backticks for code identifiers is also important.
8 / 27
Context: During a Slack discussion about debugging an issue with the AWS Lambda function, David asks Maria to clarify her explanation. Which of the following sentences best uses punctuation for clarity?
The correct answer uses a semicolon to join two related independent clauses, clearly explaining the cause and effect. The other options either omit punctuation entirely or use a comma incorrectly, leading to ambiguity about the relationship between the two statements. Maintaining clear causal links is vital in technical explanations.
9 / 27
Context: You're writing a standup update to your team about progress on the new data pipeline. Which sentence best demonstrates correct punctuation in this context?
The correct answer uses a comma to separate two related clauses describing the completed actions. The other options either omit punctuation or use an unnecessary question mark, which is inappropriate for a standup update. Focusing on what's been achieved and next steps is key.
10 / 27
Context: During a code review of the payment_processing.py module, Liam comments on Sarah's use of a conditional statement. Which option demonstrates the most appropriate punctuation for this comment?
The correct answer uses a semicolon to separate the two parts of the conditional statement, adhering to standard Python syntax. The other options incorrectly use either a colon or question mark in this context, which would be inappropriate for a code review comment. It's crucial to maintain clarity and accuracy when describing code logic.
11 / 27
Context: You're drafting the description for a Pull Request introducing a new API endpoint. Which of the following options best uses punctuation to clearly define the endpoint's purpose?
The correct answer clearly defines the endpoint's URL and its intended function using a descriptive phrase. The other options are too brief or include unnecessary details like query parameters – PR descriptions should focus on *what* the change does, not *how* it's implemented. Using backticks for code identifiers is also important.
12 / 27
Context: During a Slack discussion about debugging an issue with the AWS Lambda function, David asks Maria to clarify her explanation. Which of the following sentences best uses punctuation for clarity?
The correct answer uses a semicolon to join two related independent clauses, clearly explaining the cause and effect. The other options either omit punctuation entirely or use a comma incorrectly, leading to ambiguity about the relationship between the two statements. Maintaining clear causal links is vital in technical explanations.
13 / 27
Context: You're writing a standup update to your team about progress on the new data pipeline. Which sentence best demonstrates correct punctuation in this context?
The correct answer uses a comma to separate two related clauses describing the completed actions. The other options either omit punctuation or use an unnecessary question mark, which is inappropriate for a standup update. Focusing on what's been achieved and next steps is key.
14 / 27
Context: During a code review of the payment_processing.py module, Liam comments on Sarah's use of a conditional statement. Which option demonstrates the most appropriate punctuation for this comment?
The correct answer uses a semicolon to separate the two parts of the conditional statement, adhering to standard Python syntax. The other options incorrectly use either a colon or question mark in this context, which would be inappropriate for a code review comment. It's crucial to maintain clarity and accuracy when describing code logic.
15 / 27
Context: You're drafting the description for a Pull Request introducing a new API endpoint. Which of the following options best uses punctuation to clearly define the endpoint's purpose?
The correct answer clearly defines the endpoint's URL and its intended function using a descriptive phrase. The other options are too brief or include unnecessary details like query parameters – PR descriptions should focus on *what* the change does, not *how* it's implemented. Using backticks for code identifiers is also important.
16 / 27
Context: During a Slack discussion about debugging an issue with the AWS Lambda function, David asks Maria to clarify her explanation. Which of the following sentences best uses punctuation for clarity?
The correct answer uses a semicolon to join two related independent clauses, clearly explaining the cause and effect. The other options either omit punctuation entirely or use a comma incorrectly, leading to ambiguity about the relationship between the two statements. Maintaining clear causal links is vital in technical explanations.
17 / 27
Context: You're writing a standup update to your team about progress on the new data pipeline. Which sentence best demonstrates correct punctuation in this context?
The correct answer uses a comma to separate two related clauses describing the completed actions. The other options either omit punctuation or use an unnecessary question mark, which is inappropriate for a standup update. Focusing on what's been achieved and next steps is key.
18 / 27
John Doe, the lead engineer, sent a Slack message: 'The database_connection is down. Check the logs.' Which punctuation choice best clarifies this message for immediate action?
Using single quotation marks around the entire message preserves the exact wording of John's Slack post. Adding an exclamation mark unnecessarily emphasizes a technical issue and can be considered unprofessional in informal communication. Semicolons are typically used to separate independent clauses; here they don't serve a purpose. The double quotes accurately represent the original phrasing while maintaining clarity.
19 / 27
You're writing a Pull Request description for a change to the authentication_service API. The endpoint currently returns user details including their 'email', 'username', and 'password'. Which option demonstrates the most accurate use of punctuation when describing this endpoint's response?
Using semicolons to separate items in a list is the standard convention for technical documentation. This clearly delineates the different fields returned by the endpoint. Brackets and dashes are inappropriate here; they would suggest grouping or separating elements that aren't intended as such. The colon provides context for the following list.
20 / 27
During a standup update, Maya says: 'We've completed testing of the new image_processing module and identified one minor bug.' Which sentence best demonstrates correct punctuation in this context?
The contraction 'we've' is perfectly acceptable in a standup update. The comma after 'and' appropriately separates two independent clauses within a single sentence. Exclamation marks are generally avoided in formal updates. Semicolons would be overly formal for this situation.
21 / 27
Liam is reviewing code and comments on a function: 'The function accepts an input string, validates it against regex pattern, and returns the result.' Which option best uses punctuation to improve clarity?
Using a comma correctly separates the different actions performed by the function. This structure enhances readability and accurately reflects the technical description. The other options introduce unnecessary punctuation or change the grammatical structure of the sentence inappropriately. The colon would be incorrect here.
22 / 27
Alex is writing a Slack message to report an error with the new microservice. He types: 'Error: Service X unavailable. Retries failed.' Which punctuation choice best clarifies this message for immediate action and signals urgency?
The correct answer uses a period to end the message, signaling a complete thought and concluding the report. Option 1 incorrectly maintains the original text without punctuation. Options 3 & 4 incorrectly use semicolons which are generally not appropriate for short, direct statements like this in Slack – they imply a more complex relationship between clauses.
23 / 27
Liam is writing a comment for a new function. He wants to clearly explain the purpose of the function and its inputs. Which option best demonstrates correct punctuation for this context?
'This function takes a string, converts it to lowercase and returns the result.'
Option A uses correct punctuation for a technical description – commas separate items in a list. The other options incorrectly use periods or single quotes where commas are needed, disrupting the flow of information. This demonstrates understanding of clarity and precision when documenting code.
24 / 27
Maria needs to draft a Slack message to inform her team about a potential issue with the CI/CD pipeline. Which sentence best uses punctuation to clearly convey the urgency of the situation?
'The build failed due to a timeout error. We need to investigate immediately.'
Option B uses a period correctly to end the sentence, signaling a complete thought. The other options incorrectly use semicolons or commas which are not appropriate for indicating urgency in this context. This demonstrates understanding of Slack etiquette.
25 / 27
David is writing a Pull Request description for a change that adds logging to a module. Which option best uses punctuation to clearly define the endpoint's purpose?
'This PR adds logging functionality to track request execution and identify potential bottlenecks.'
Option B is the most precise. The period clearly separates the description from the action being taken. The other options incorrectly use commas or conjunctions which can create ambiguity. This demonstrates a good understanding of PR descriptions.
26 / 27
Sarah is preparing a standup update for her team about a bug fix. Which sentence best demonstrates correct punctuation in this context?
'We fixed the issue with the database connection and improved performance.'
Option B uses a comma correctly to join two related clauses. The other options incorrectly use semicolons or conjunctions which create an awkward flow. This demonstrates understanding of clear, concise communication during standups.
27 / 27
John Doe needs to write a comment for a code review of a function that calculates the total price of an order. Which option demonstrates the most appropriate punctuation for this comment?
'The function calculates the total price by summing up the item prices and applying the tax rate.'
Option B correctly uses 'and' to connect two related actions within a single sentence. The other options incorrectly use semicolons or commas which disrupt the flow of information and create ambiguity. This demonstrates understanding of code review best practices.
What will I practise in "Punctuation in Technical Writing — IT English Grammar Exercise"?
Practise colons, semicolons, em-dashes, the Oxford comma, and compound-adjective hyphens in technical documentation, PR descriptions, and IT writing.
How many exercises are in this module?
This module has 27 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.