5 exercises — backward references, cross-references, and citing decisions in technical specifications and RFCs.
Key patterns:
As described above / as mentioned in — backward references within a document
Refer to [Title/Section] — directs reader to another document or section
As agreed in [context] on [date] — traces a decision to its source
In line with / as per / consistent with — signals alignment with a prior requirement
0 / 5 completed
1 / 5
A technical specification refers the reader to an earlier section. Which sentence uses referencing language most precisely?
"As described above" is a backward reference marker that links the current section to earlier content without repeating it. This improves document coherence while keeping each section concise. It is one of the standard cohesive devices in technical writing alongside as mentioned, as noted, and as outlined in Section 3. Option A is informal; option C is unprofessional; option D is vague. Related patterns: "as mentioned in the requirements", "see Section 4 for details".
2 / 5
An RFC cross-references a related document. Which sentence demonstrates the best cross-referencing practice?
"Refer to [Title]" is the standard cross-referencing verb in technical documents. Providing the full document title (or number) makes the reference actionable and unambiguous. RFC and ADR conventions typically require exact document identifiers for cross-references so that readers and tools can locate them automatically. Vague references (option A, C, D) break the information chain. Related patterns: "as detailed in the companion document", "in accordance with ADR-012", "see also Section 6.2".
3 / 5
A design document includes a decision made in a previous meeting. Choose the sentence that most professionally references that decision:
"As agreed in [context] on [date]" provides a precise, traceable reference to a prior decision. Including the context (architecture review) and date makes it possible for readers to verify the decision in meeting notes or Confluence. This is standard practice in design documents and ADRs where traceability of decisions is important. Options B, C, and D all fail to provide the provenance of the decision. Related patterns: "as noted in the sprint retrospective", "in line with the decision taken on", "referring back to the agreed approach".
4 / 5
An API guide wants to direct readers to a more detailed section for error handling. Which sentence is most effective?
"For [topic], see [section title/location]" is the standard forward-reference pattern in API and technical documentation. It tells the reader exactly what they will find and exactly where to find it. The phrase "a complete list" sets expectations about the scope of the referenced section, which reduces frustration. Options A, C, and D are vague or informal and fail to give the reader actionable direction. Related patterns: "for further details, refer to", "this is covered in depth in Section 5".
5 / 5
A postmortem action item list cross-references the requirements document. Choose the sentence that correctly uses "in line with":
"In line with [document/agreement]" signals that an action or decision is consistent with a previously established requirement or agreement. It is a referencing phrase that adds authority to the action item by grounding it in a named source. Providing the document identifier (REQ-007) makes the reference traceable. Options B, C, and D are vague and fail to provide the traceability that postmortems require. Related patterns: "as required by", "consistent with the SLA defined in", "as per the agreed architecture".