5 exercises — practise choosing between declarative, imperative, interrogative, and exclamative sentences for different IT communication contexts.
0 / 5 completed
1 / 5
A technical writer is documenting a setup procedure. Which sentence type is most appropriate for each step in the instructions?
Imperative sentences ("Install Node.js version 20 or higher") are the standard for step-by-step technical instructions. They are direct, concise, and action-oriented — the verb leads, which mirrors the action the user must perform. This is the convention across all major style guides (Google, Microsoft, Apple, Mozilla). Declarative alternatives ("The user should install...") are longer and slightly softer — acceptable in narrative documentation but unnecessarily wordy for numbered steps. Interrogative steps ("Have you installed...?") read like a checklist, not an instruction. The imperative is the global technical writing standard for procedures.
2 / 5
Which use of interrogative form is appropriate in technical documentation?
Option A — using an interrogative as a section heading in a troubleshooting guide ("Why does this error occur?", "How do I reset my password?", "What is the difference between X and Y?") — is a well-established convention. It mirrors how users think and search ("why does this happen?") and is used by AWS, Google Cloud, Stripe, and others in their FAQ and troubleshooting sections. Option B ("Is the server running?") as a deployment step is interrogative used as a checklist item — acceptable but non-standard for a guide. Option C as a test file title is unusual — test files typically use descriptive noun phrases or imperative function names. Option A is the clearest, most conventionally appropriate use.
3 / 5
Which sentence is more appropriate for an API reference entry describing what a function does?
Both the imperative ("Call getUser() to retrieve...") and the declarative ("getUser() retrieves...") are standard in API documentation and represent two different but equally accepted conventions. The imperative (Option A) is action-focused and common in tutorial-style or task-oriented docs: it tells the developer what to do. The declarative (Option B) is reference-focused — it describes what the function does, which is the convention in many formal API references (MDN, Javadoc, Python standard library). Option C is weaker: "if you want to" is unnecessarily hedged and conversational for a reference. Choose one style per document and apply it consistently.
4 / 5
A developer is leaving a code review comment. Which formulation most effectively uses interrogative structure?
"Does this handle empty input? I don't see a null check." (Option B) is the most effective code review comment. The interrogative frame ("Does this handle...?") softens the feedback — it invites the author to respond or clarify, acknowledges that the reviewer may have missed something, and reduces the confrontational tone. This is the recommended approach in many engineering culture guides (e.g., Google's code review guide). Option A (declarative) is direct but could come across as blunt. Option C ("You forgot") is accusatory — making the comment personal rather than about the code. Option D uses exclamation marks — inappropriate and aggressive. Code review convention: frame concerns as questions or observations, not accusations.
5 / 5
Which statement about exclamative sentences in technical communication is most accurate?
Option B correctly identifies the register boundary for exclamative sentences. In informal IT communication — Slack celebrations ("The deploy went through!"), team announcements ("We hit 1M users!"), internal social posts — exclamatives are natural and positive. They reinforce team morale. However, in technical documentation, API references, error messages, code reviews, and formal reports, exclamative sentences are unprofessional. They undermine credibility ("What an elegant algorithm!" in a spec reads as subjective and fluffy). Error messages should be calm and actionable — not exclamative ("Critical error!" is common but borderline; "Error: Connection refused. Check your network." is better). The rule: exclamatives belong in human, social communication — not in technical reference material.