Punctuation with Quotation Marks Around Technical Terms
5 exercises — practise placing punctuation correctly with quoted error messages, code strings, and CLI flags.
0 / 20 completed
1 / 20
Which sentence correctly places the comma inside the closing quotation mark around a quoted error message, following standard American technical-writing convention?
"...shows \"connection refused,\" which usually points to a firewall rule" is correct under standard American convention: the comma goes inside the closing quotation mark. Option B places the comma outside, which is the British convention and inconsistent if the rest of the document follows American style. Option C adds an incorrect space before the comma. Option D misplaces the comma before the quotation and omits it after.
2 / 20
Choose the sentence that correctly keeps a literal error string unmodified, placing punctuation outside the quotation marks because moving it inside would corrupt the exact string being referenced.
"...the exact string \"user_not_found\"; no trailing period..." is correct: when quoting a precise code identifier or string literal, punctuation that is not part of the literal string stays outside the quotation marks, so the reader can trust the quoted content is exact. Option B incorrectly moves the semicolon inside, implying it's part of the string. Option C adds a fabricated period that was never in the original string. Option D adds an incorrect space before the semicolon.
3 / 20
Which sentence correctly punctuates a sentence that ends with a quoted CLI flag, following American convention for periods?
"Always pass the flag \"--dry-run.\"" is correct under American convention: the period goes inside the closing quotation mark, even though it's not literally part of the flag string. Option B places the period outside, following British style instead. Option C adds a stray space before the period. Option D omits the sentence-ending period entirely.
4 / 20
Select the sentence that correctly places a question mark outside the quotation marks because the question mark belongs to the whole sentence, not to the quoted term itself.
"...include the header \"X-Request-Id\"?" is correct: since the question mark applies to the entire sentence and "X-Request-Id" itself is not a question, the question mark goes outside the closing quotation mark, overriding the usual inside-placement rule for periods and commas. Option B incorrectly places it inside, implying the header name itself is a question. Option C adds an extra, unnecessary quotation mark. Option D adds a stray space before the question mark.
5 / 20
Which sentence correctly punctuates a colon that introduces a code block, keeping the colon outside the quoted term since it belongs to the introducing sentence?
"...variable \"NODE_ENV\": it controls which config file loads" is correct: colons and semicolons always go outside closing quotation marks in both American and British conventions, since they punctuate the surrounding sentence, not the quoted term. Option B incorrectly moves the colon inside the quotation marks, implying it's part of the variable name. Option C adds a stray space before the colon. Option D adds an unnecessary comma and a nonsensical trailing word.
6 / 20
Alex: 'The server timed out after 30 seconds.' I'm seeing a high error rate here. Should I add this to the release notes?
This question tests using quotation marks around a specific error message. The correct punctuation involves enclosing the quoted text within single quotes to maintain its exact form and clarity. Adding a comma before the quote as in option B is incorrect; it disrupts the precise representation of the technical detail. Option C is also wrong as it treats the entire phrase as an instruction, not a direct observation.
7 / 20
During code review, Sarah commented: 'This function doesn't handle null values correctly.' What's the best way to respond in Slack?
This scenario tests punctuation when communicating a technical issue in a real-time chat environment. While quotation marks can be used for emphasis, the most appropriate approach here is to simply quote the comment verbatim as shown in option 3. This preserves the original wording and avoids adding unnecessary formatting or altering the meaning of Sarah's statement. Options A & B are overly verbose; option C incorrectly uses single quotes.
8 / 20
In a PR description for a new feature, Ben writes: 'The API returns a 404 error if the resource doesn't exist.' What punctuation is most appropriate?
This question assesses punctuation within a longer PR description. The correct approach is to simply quote the text verbatim as in option 3. Using quotation marks around '404 error' (option B) is unnecessary and potentially misleading – it suggests that '404 error' is itself a variable or code element. Option A incorrectly treats the entire phrase as a specific response; Option C uses single quotes, which isn't standard practice here.
9 / 20
David posted this message to the team channel: 'Use --verbose flag for debugging.' Is this grammatically correct?
This tests the use of quotation marks around commands and flags in a Slack environment. The correct answer involves enclosing the entire phrase within single quotes to preserve the exact wording of David's message. Note that the backticks are used to represent the command itself, not as punctuation. Option B incorrectly uses single quotes around the command flag; option C adds an unnecessary period and option D misinterprets the message.
10 / 20
Maria wrote in a standup update: 'The new feature uses the Kafka protocol.' What punctuation is appropriate here?
This scenario focuses on using quotation marks for technical terms in a standup update. The correct approach is to enclose the term 'Kafka' within single quotes as shown in option 1. This indicates that it's a specific product name and not part of a larger instruction or description. Option B incorrectly uses single quotes around the entire protocol name; option C adds an unnecessary period, and option D misinterprets the update.
11 / 20
Alex: 'The server timed out after 30 seconds.' I'm seeing a high error rate here. Should I add this to the release notes?
This question tests using quotation marks around a specific error message. The correct punctuation involves enclosing the quoted text within single quotes to maintain its exact form and clarity. Adding a comma before the quote as in option B is incorrect; it disrupts the precise representation of the technical detail. Option C is also wrong as it treats the entire phrase as an instruction, not a direct observation.
12 / 20
During code review, Sarah commented: 'This function doesn't handle null values correctly.' What's the best way to respond in Slack?
This scenario tests punctuation when communicating a technical issue in a real-time chat environment. While quotation marks can be used for emphasis, the most appropriate approach here is to simply quote the comment verbatim as shown in option 3. This preserves the original wording and avoids adding unnecessary formatting or altering the meaning of Sarah's statement. Options A & B are overly verbose; option C incorrectly uses single quotes.
13 / 20
In a PR description for a new feature, Ben writes: 'The API returns a 404 error if the resource doesn't exist.' What punctuation is most appropriate?
This question assesses punctuation within a longer PR description. The correct approach is to simply quote the text verbatim as in option 3. Using quotation marks around '404 error' (option B) is unnecessary and potentially misleading – it suggests that '404 error' is itself a variable or code element. Option A incorrectly treats the entire phrase as a specific response; Option C uses single quotes, which isn't standard practice here.
14 / 20
David posted this message to the team channel: 'Use --verbose flag for debugging.' Is this grammatically correct?
This tests the use of quotation marks around commands and flags in a Slack environment. The correct answer involves enclosing the entire phrase within single quotes to preserve the exact wording of David's message. Note that the backticks are used to represent the command itself, not as punctuation. Option B incorrectly uses single quotes around the command flag; option C adds an unnecessary period and option D misinterprets the message.
15 / 20
Maria wrote in a standup update: 'The new feature uses the Kafka protocol.' What punctuation is appropriate here?
This scenario focuses on using quotation marks for technical terms in a standup update. The correct approach is to enclose the term 'Kafka' within single quotes as shown in option 1. This indicates that it's a specific product name and not part of a larger instruction or description. Option B incorrectly uses single quotes around the entire protocol name; option C adds an unnecessary period, and option D misinterprets the update.
16 / 20
Alex: 'The server timed out after 30 seconds.' I'm seeing a high error rate here. Should I add this to the release notes?
This question tests using quotation marks around a specific error message. The correct punctuation involves enclosing the quoted text within single quotes to maintain its exact form and clarity. Adding a comma before the quote as in option B is incorrect; it disrupts the precise representation of the technical detail. Option C is also wrong as it treats the entire phrase as an instruction, not a direct observation.
17 / 20
During code review, Sarah commented: 'This function doesn't handle null values correctly.' What's the best way to respond in Slack?
This scenario tests punctuation when communicating a technical issue in a real-time chat environment. While quotation marks can be used for emphasis, the most appropriate approach here is to simply quote the comment verbatim as shown in option 3. This preserves the original wording and avoids adding unnecessary formatting or altering the meaning of Sarah's statement. Options A & B are overly verbose; option C incorrectly uses single quotes.
18 / 20
In a PR description for a new feature, Ben writes: 'The API returns a 404 error if the resource doesn't exist.' What punctuation is most appropriate?
This question assesses punctuation within a longer PR description. The correct approach is to simply quote the text verbatim as in option 3. Using quotation marks around '404 error' (option B) is unnecessary and potentially misleading – it suggests that '404 error' is itself a variable or code element. Option A incorrectly treats the entire phrase as a specific response; Option C uses single quotes, which isn't standard practice here.
19 / 20
David posted this message to the team channel: 'Use --verbose flag for debugging.' Is this grammatically correct?
This tests the use of quotation marks around commands and flags in a Slack environment. The correct answer involves enclosing the entire phrase within single quotes to preserve the exact wording of David's message. Note that the backticks are used to represent the command itself, not as punctuation. Option B incorrectly uses single quotes around the command flag; option C adds an unnecessary period and option D misinterprets the message.
20 / 20
Maria wrote in a standup update: 'The new feature uses the Kafka protocol.' What punctuation is appropriate here?
This scenario focuses on using quotation marks for technical terms in a standup update. The correct approach is to enclose the term 'Kafka' within single quotes as shown in option 1. This indicates that it's a specific product name and not part of a larger instruction or description. Option B incorrectly uses single quotes around the entire protocol name; option C adds an unnecessary period, and option D misinterprets the update.
What will I practise in "Punctuation with Quotation Marks Around Technical Terms — IT Grammar Exercise"?
Practise correctly placing commas, periods, colons, semicolons, and question marks relative to closing quotation marks around technical terms, error strings
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.