5 exercises — learn when fragments are acceptable and when complete sentences are required in technical documentation, UIs, and error messages.
0 / 18 completed
1 / 18
Which statement about sentence fragments in bulleted lists is correct?
Technical documentation widely accepts fragment bullet points — provided all items in the list are grammatically parallel. Example of acceptable fragments: "• Improved query performance / • Reduced memory usage / • Fixed authentication timeout" — noun phrases, parallel. Unacceptable mix: "• Improved query performance / • The authentication timeout was fixed" — mixes fragment with full sentence, breaking parallelism. The key rule is consistency and parallelism within a list, not whether each bullet is a complete sentence. Style guides (Google, Microsoft, Apple) all permit fragment bullets.
2 / 18
Which is the most appropriate error message for a production application?
"The requested file was not found on the server." is the most appropriate for a production error message. It is a complete sentence with subject, verb, and context — it tells the user what happened and where. Option A ("File not found.") is a standard, widely-recognised fragment acceptable in many contexts (HTTP 404 messages, log output, mobile notifications) but lacks the politeness and detail expected in a polished application UI. Option C is fragmented and unclear. Option D is overly wordy and informal ("at this time" is filler). For user-facing errors, prefer complete, concise sentences; for log files and developer tools, shorter fragments are acceptable.
3 / 18
Which use of a fragment is most appropriate in a user interface?
"Save changes" is the correct imperative fragment for a UI button label. UI microcopy (labels, buttons, menu items, tooltips) universally uses imperative verb phrases or compact noun phrases — never full sentences. Full sentences on buttons are verbose and visually cluttered. Standard patterns: "Save changes", "Delete account", "Run tests", "View report". These are not errors; they are the expected and professional style for interface labels. Option C ("Changes saved when you click here") is a confusing mix of present and future. Option D uses a gerund phrase, making the label sound nominal and vague.
4 / 18
A developer is writing step-by-step installation instructions. Which approach is most appropriate?
Both imperative fragment steps (Option A style) and complete-sentence steps (Option B style) are used in professional technical documentation — the choice depends on context. Fragment steps ("Open terminal", "Run install command") are common in quick-start guides, CLI documentation, and developer-facing READMEs where brevity is valued. Complete-sentence steps are preferred in formal user manuals, enterprise documentation, and content aimed at less technical audiences. Option C (mixing both) breaks parallelism and is always wrong. The consistent application of one style throughout a document is the critical rule.
5 / 18
Which passage is most appropriate for the body text of a formal technical specification document?
Formal technical specification documents (RFCs, SRS documents, architecture specs) require complete sentences. Option B is correct: one coherent sentence with clear syntactic relationships between subject ("the system"), verb ("shall authenticate"), object ("all API requests"), and modifiers ("using OAuth 2.0 before processing them"). Option A contains unacceptable fragments in formal prose — "Using OAuth 2.0." and "Before processing." are dangling modifiers that lack a main clause. Option C is appropriate for a bullet list but not for body prose. Option D — a series of em-dash fragments — is suitable for informal notes, not specification documents.
6 / 18
Slack Message: 'We're seeing high latency with the new feature. Check the logs.' This Slack message contains a sentence fragment. Which option best describes why it's problematic?
This focuses on clarity in informal communication. While Slack messages can be less formal, sentence fragments create ambiguity. 'Check the logs' needs to be more specific (e.g., 'Review the application logs for error messages'). The other options either accept unacceptable vagueness or misinterpret the nature of technical jargon.
7 / 18
PR Description: 'The new service handles user authentication. It uses JWT.' This PR description contains a fragment. What adjustment would improve its clarity and adherence to documentation standards?
This assesses understanding of technical documentation best practices. Sentence fragments can obscure meaning and lack context. Adding an explanation for JWT clarifies its role in the authentication process, making the PR description more informative and understandable to a wider audience. Simply removing information is not ideal as it leaves the reader without crucial details.
8 / 18
Slack Message: 'We're seeing high latency with the new feature. Check the logs.' This Slack message contains a sentence fragment. Which option best describes why it's problematic?
This focuses on clarity in informal communication. While Slack messages can be less formal, sentence fragments create ambiguity. 'Check the logs' needs to be more specific (e.g., 'Review the application logs for error messages'). The other options either accept unacceptable vagueness or misinterpret the nature of technical jargon.
9 / 18
PR Description: 'The new service handles user authentication. It uses JWT.' This PR description contains a fragment. What adjustment would improve its clarity and adherence to documentation standards?
This assesses understanding of technical documentation best practices. Sentence fragments can obscure meaning and lack context. Adding an explanation for JWT clarifies its role in the authentication process, making the PR description more informative and understandable to a wider audience. Simply removing information is not ideal as it leaves the reader without crucial details.
10 / 18
Slack Message: 'We're seeing high latency with the new feature. Check the logs.' This Slack message contains a sentence fragment. Which option best describes why it's problematic?
This focuses on clarity in informal communication. While Slack messages can be less formal, sentence fragments create ambiguity. 'Check the logs' needs to be more specific (e.g., 'Review the application logs for error messages'). The other options either accept unacceptable vagueness or misinterpret the nature of technical jargon.
11 / 18
PR Description: 'The new service handles user authentication. It uses JWT.' This PR description contains a fragment. What adjustment would improve its clarity and adherence to documentation standards?
This assesses understanding of technical documentation best practices. Sentence fragments can obscure meaning and lack context. Adding an explanation for JWT clarifies its role in the authentication process, making the PR description more informative and understandable to a wider audience. Simply removing information is not ideal as it leaves the reader without crucial details.
12 / 18
During a code review of a new API endpoint, Alice comments: 'The function returns data. It's JSON.' This statement contains a sentence fragment. Which of the following best explains why this is problematic from a documentation perspective? Returns could be improved.
Sentence fragments lack a complete thought and can lead to ambiguity. In documentation, clarity is paramount, particularly when describing API responses. The fragment 'The function returns data' doesn't specify the format or contents of that data (e.g., JSON structure), making it difficult for another developer to understand how to use the endpoint effectively. A more complete statement would detail the expected data structure.
13 / 18
Ben is writing a Slack message about a recent deployment. He types: 'New version deployed. Users can now access feature X.' Which of the following best describes why this communication needs improvement regarding sentence fragments? The user experience description is incomplete.
While Slack messages can be informal, clear communication in IT documentation requires a degree of formality. The fragment 'New version deployed. Users can now access feature X' lacks crucial information – confirmation of deployment success and a brief description of the new functionality. This leaves the recipient uncertain about whether the deployment was successful and what they are actually accessing.
14 / 18
Sarah is drafting an API response message for a failed authentication attempt. She writes: 'Error code: 401. User not found.' This message contains a sentence fragment. Which of the following adjustments would be most effective in improving its clarity and adherence to API documentation best practices?
The primary issue with the original message is its lack of context. While the error code and reason are provided, a more robust API response should clearly state the *outcome* of the failed authentication attempt. Adding 'User authentication failed' provides this crucial information, improving understanding for developers consuming the API. Option B is also good but less immediately helpful than stating the outcome.
15 / 18
Mark is writing a Slack message to announce a bug fix for a critical component. He types: 'Fixed issue with database connection. System now stable.' This message contains a sentence fragment. Which of the following best describes why this communication needs improvement regarding clarity and documentation standards?
While brevity is often desired in Slack, this message lacks crucial context. Simply stating 'Fixed issue with database connection' doesn't explain the *nature* of the bug or its potential impact on users or other system components. Adding details about the root cause (e.g., 'Resolved a deadlock preventing data access') would significantly improve understanding and facilitate future troubleshooting. Option D is incorrect; the message *does* require improvement.
16 / 18
Raj is documenting a new feature in the application's technical specifications. He writes: 'The module handles user input. It validates data.' This passage contains a sentence fragment. Which of the following best describes why this adjustment would improve its clarity and adherence to documentation standards?
Technical specifications require precise language. While 'The module handles user input' is a functional description, it lacks context. Adding 'The module processes user input' immediately clarifies its role within the application. Furthermore, specifying *how* the data is validated (even briefly) would strengthen the documentation and ensure developers understand how to interact with the feature correctly. Option D is incorrect; formal technical specifications demand greater precision.
17 / 18
Elena is drafting a Slack message to update her team on a deployment. She types: 'Deployment complete. Service X is live.' This message contains a sentence fragment. Which of the following best describes why this communication needs improvement regarding standard documentation practices?
While 'live' can be imprecise, the fundamental issue here is the fragmented structure. The message needs to explicitly state that the service *is available* for users or systems to interact with. A complete sentence would provide more valuable information about the deployment's scope and potential impact – this is crucial context for a team update.
18 / 18
Chris is documenting a new feature in an API response: 'The endpoint returns user information. It includes name and email.' This passage contains a sentence fragment. What would be the MOST appropriate addition to improve this documentation?
While all options are potentially useful, specifying the data types is crucial for developers to correctly parse and interpret the API response. This provides essential information about how to handle the returned data, addressing the fundamental problem of the fragmented sentence.
What will I practise in "Sentence Fragments in IT Documentation — Grammar Exercise"?
Learn when sentence fragments are acceptable in technical writing: bullet points, error messages, UI labels, step-by-step instructions, and formal
How many exercises are in this module?
This module has 18 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.