A technical tutorial is a "Linear Contract" with the user. If a step is missing, duplicated, or out of order, the contract is broken, and the user's progress is halted. The Step Numbering Logic rule is a forensic structural validator that ensures your "How-To" content follows a flawless, sequential path, guiding the user from start to finish with mathematical certainty.
This rule performs a "Sequence Audit" on every numbered list in your document. It detects "Tutorial Gaps"—where a writer jumps from Step 2 to Step 4—and "Duplicate Anchors," where multiple steps share the same number. For complex guides, it also manages "Sub-step Integrity," ensuring that nested items (e.g., 1.1, 1.2) are correctly anchored to their parent steps. This eliminates the "Broken Instruction" problem that plagues multi-contributor documentation projects, ensuring a smooth, predictable path for every user.
Beyond simple numbering, the rule enforces an "Imperative Style" baseline. Technical instructions should be actionable and direct. Our "Verb Sieve" scans the start of every step for active language (e.g., "Run," "Install," "Click"). If a step starts with passive or weak language (e.g., "Then you can maybe try to..."), it is flagged for refactoring. This enforces a "Command Voice" that builds user confidence and reduces the cognitive load required to follow complex technical procedures.
"Code-Step Linkage" is another critical feature. In modern technical writing, a step that describes an action should almost always be followed by the specific command or code block that performs that action. Our auditor identifies "Ghost Instructions"—steps that mention a "command" or "script" but are not followed by a code block. This ensures that your tutorials are high-fidelity assets where the theory (the text) and the practice (the code) are perfectly synchronized.
The rule also manages "Punctuation Uniformity." When one step ends with a period and the next does not, the document feels unpolished. Our "Punctuation Sync" detects these stylistic deviations and requires the freelancer to maintain a consistent standard. While seemingly small, this level of consistency is a primary marker of professional-grade technical documentation. It transforms a "Rough Draft" into a "Published Asset" that meets the highest standards of corporate communication.
Clarity is the ultimate goal of technical documentation. The Step Numbering Logic rule ensures that your instructions are as logical as they are actionable, protecting your users from confusion and your brand from the reputation of having "unusable" guides.