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 / 20 completed
1 / 20
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 / 20
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 / 20
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 / 20
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 / 20
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".
6 / 20
During a code review of the authenticationService.js module, Liam comments: 'This function needs to validate against the user's profile data, as outlined in section 3.2 of the API specification.' Which phrasing best demonstrates precise referencing?
The key here is specificity. Option 2 directly references the document and section number, providing a clear point of reference. Options A and B are too vague, while option D introduces unrelated concerns about completeness – the question focuses on *how* to refer, not whether the code is complete.
7 / 20
Sarah sends a Slack message to the team: 'As discussed in yesterday's standup, we're moving forward with the database migration. Please review the updated deployment instructions.' Which sentence exemplifies best practice for referencing a previous discussion?
Context is crucial. Option 2 subtly reminds recipients of the source without being overly prescriptive. Options A and B are too informal, while option D shifts the focus to a new discussion instead of referencing the previous one.
8 / 20
In a Pull Request description for a change to the payment processing API, David writes: 'This update aligns with the requirements outlined in document RND-1234.' Which sentence best demonstrates accurate referencing of a requirement document?
Precision matters. Option 1 explicitly connects the change to the specific requirement document (RND-1234). Options A and B are too general, and option D simply asks for a review without referencing the source of requirements.
9 / 20
The API documentation for handling rate limits includes this sentence: 'If you exceed the limit, please refer to section 4.2 for retry strategies.' Which of the following best illustrates effective referencing within an API guide?
Clarity is key. Option 2 clearly directs the user to the relevant section and explains its purpose (retry strategies). Options A and B are too vague, while option D introduces unrelated information about the rate-limiting system itself.
10 / 20
During a postmortem meeting about a recent outage, Maria states: 'The root cause was identified as insufficient logging. This is in line with the recommendations outlined in the incident response plan.' Which sentence best exemplifies appropriate referencing of a documented process?
Linking back is crucial. Option 1 directly connects the identified root cause to the specific recommendation within the incident response plan. This demonstrates that actions are being taken in accordance with established procedures, avoiding ambiguity and promoting accountability.
11 / 20
During a code review of the authenticationService.js module, Liam comments: 'This function needs to validate against the user's profile data, as outlined in section 3.2 of the API specification.' Which phrasing best demonstrates precise referencing?
The key here is specificity. Option 2 directly references the document and section number, providing a clear point of reference. Options A and B are too vague, while option D introduces unrelated concerns about completeness – the question focuses on *how* to refer, not whether the code is complete.
12 / 20
Sarah sends a Slack message to the team: 'As discussed in yesterday's standup, we're moving forward with the database migration. Please review the updated deployment instructions.' Which sentence exemplifies best practice for referencing a previous discussion?
Context is crucial. Option 2 subtly reminds recipients of the source without being overly prescriptive. Options A and B are too informal, while option D shifts the focus to a new discussion instead of referencing the previous one.
13 / 20
In a Pull Request description for a change to the payment processing API, David writes: 'This update aligns with the requirements outlined in document RND-1234.' Which sentence best demonstrates accurate referencing of a requirement document?
Precision matters. Option 1 explicitly connects the change to the specific requirement document (RND-1234). Options A and B are too general, and option D simply asks for a review without referencing the source of requirements.
14 / 20
The API documentation for handling rate limits includes this sentence: 'If you exceed the limit, please refer to section 4.2 for retry strategies.' Which of the following best illustrates effective referencing within an API guide?
Clarity is key. Option 2 clearly directs the user to the relevant section and explains its purpose (retry strategies). Options A and B are too vague, while option D introduces unrelated information about the rate-limiting system itself.
15 / 20
During a postmortem meeting about a recent outage, Maria states: 'The root cause was identified as insufficient logging. This is in line with the recommendations outlined in the incident response plan.' Which sentence best exemplifies appropriate referencing of a documented process?
Linking back is crucial. Option 1 directly connects the identified root cause to the specific recommendation within the incident response plan. This demonstrates that actions are being taken in accordance with established procedures, avoiding ambiguity and promoting accountability.
16 / 20
During a code review of the authenticationService.js module, Liam comments: 'This function needs to validate against the user's profile data, as outlined in section 3.2 of the API specification.' Which phrasing best demonstrates precise referencing?
The key here is specificity. Option 2 directly references the document and section number, providing a clear point of reference. Options A and B are too vague, while option D introduces unrelated concerns about completeness – the question focuses on *how* to refer, not whether the code is complete.
17 / 20
Sarah sends a Slack message to the team: 'As discussed in yesterday's standup, we're moving forward with the database migration. Please review the updated deployment instructions.' Which sentence exemplifies best practice for referencing a previous discussion?
Context is crucial. Option 2 subtly reminds recipients of the source without being overly prescriptive. Options A and B are too informal, while option D shifts the focus to a new discussion instead of referencing the previous one.
18 / 20
In a Pull Request description for a change to the payment processing API, David writes: 'This update aligns with the requirements outlined in document RND-1234.' Which sentence best demonstrates accurate referencing of a requirement document?
Precision matters. Option 1 explicitly connects the change to the specific requirement document (RND-1234). Options A and B are too general, and option D simply asks for a review without referencing the source of requirements.
19 / 20
The API documentation for handling rate limits includes this sentence: 'If you exceed the limit, please refer to section 4.2 for retry strategies.' Which of the following best illustrates effective referencing within an API guide?
Clarity is key. Option 2 clearly directs the user to the relevant section and explains its purpose (retry strategies). Options A and B are too vague, while option D introduces unrelated information about the rate-limiting system itself.
20 / 20
During a postmortem meeting about a recent outage, Maria states: 'The root cause was identified as insufficient logging. This is in line with the recommendations outlined in the incident response plan.' Which sentence best exemplifies appropriate referencing of a documented process?
Linking back is crucial. Option 1 directly connects the identified root cause to the specific recommendation within the incident response plan. This demonstrates that actions are being taken in accordance with established procedures, avoiding ambiguity and promoting accountability.
What will I practise in "Referencing Language in Technical Documents — IT Grammar Exercise"?
Practice referring to earlier content, cross-referencing, and citing decisions in technical specs, RFCs, and design documents. 5 exercises, Intermediate level.
How many exercises are in this module?
This module has 20 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.