Imperative Instructions in Technical Documentation
5 exercises — using the imperative mood correctly in CLI guides, runbooks, and setup documentation: Run, Navigate, Ensure, Note that.
0 / 5 completed
1 / 5
Which version of a CLI instruction uses the imperative mood correctly?
Option B uses the imperative mood: "Run" — bare infinitive as a direct instruction. Technical documentation (READMEs, CLI guides, runbooks, installation steps) uses the imperative because it is the most direct and concise form. Option A adds "You should" — this softens the instruction into a recommendation, which is less clear for procedures where the action is required. Option C uses passive voice — less direct and appropriate for documentation of what a system does, not what the user should do. Option D is a conditional prediction, not an instruction. Rule: start each step with a base verb: Run, Navigate, Ensure, Install, Set, Copy.
2 / 5
A runbook step reads: "Navigate to the configuration directory." Which rewrite maintains the imperative style but adds more precision?
Option B keeps the imperative ("Navigate to") and adds precision with a specific path (/etc/myapp/config/) and a non-defining relative clause explaining what is there. Option A uses "You should" (softens unnecessarily) and "where the config files are located" (verbose). Option C uses a gerund to name the step — appropriate for section headings but not for the instruction itself. Option D uses third person — wrong for instructions directed at the user. Best practice for runbooks: Navigate to [exact path]. Create [specific file]. Verify that [condition].
3 / 5
Which sentence correctly uses "Ensure that" in a technical checklist?
Option A is correct. "Ensure that" introduces a requirement clause: Ensure that [subject] [verb phrase]. It is an imperative that tells the user what condition must be true before proceeding. Option B redundantly uses both "must" before "ensure" and "must be set" inside — the imperative form of "ensure" is already strong. Option C converts to a gerund phrase and loses the directive force. Option D repeats "ensure/ensuring" redundantly. Use "Ensure that" to verify pre-conditions: "Ensure that the service is stopped before applying the patch." "Ensure that all tests pass before merging."
4 / 5
A documentation note uses "Note that". Which version is correct and professional?
Option B is the most professional form. "Note that" is an imperative followed directly by a subordinate clause (no colon needed after "Note that"). It draws attention to important information. Option A incorrectly inserts a colon after "Note that" — the colon is used after "Note:" (the abbreviated form) but not after "Note that". Option C uses "Note:" which is an acceptable abbreviated alternative, but the question specifies "Note that". Option D adds "Please" — this is appropriate for conversational context but unnecessary in technical documentation; imperative instructions are direct without "please". The two accepted forms: Note that [clause] and Note: [statement].
5 / 5
Which ordered step uses the best imperative style for CLI documentation?
Option C is correct. It uses two imperative verbs: "Copy" and "update". The coordinating structure "Copy X, then update Y" chains two instructions clearly. Option A uses "should" (softens) and "they then need to" (wrong person — not "they", the documentation addresses "you" directly, or preferably no pronoun at all). Option B uses "would" (conditional rather than directive) and the verbose "after that you put in". Option D uses gerunds — appropriate for section headings but not step instructions. CLI documentation standard: each step is a command, starting with a verb. Complex steps use comma + "then" or split into two numbered steps.