5 exercises — using exophoric references like "as shown above" and "see Figure 3" correctly, and converting fragile live-context pointers into durable written ones for postmortems and runbooks.
0 / 5 completed
1 / 5
A design doc says: "As shown above, the latency spikes correlate with GC pauses." What kind of reference is "as shown above", and how does it differ from anaphora?
Option B is correct. Exophoric reference points outside the text to something in the shared context — a chart, screenshot, diagram, or physical surroundings — rather than to another word within the discourse itself. "As shown above" typically points to a figure or graph embedded in the document, not to a specific noun phrase mentioned in prior sentences. This differs from anaphora (referring back to a previously mentioned word/phrase within the text, e.g., "the server crashed; it then restarted", where "it" = "the server") and cataphora (referring forward within the text, e.g., "Here's what happened: the server crashed"). Common exophoric markers in technical writing: "as shown above/below", "see Figure 3", "as illustrated in the diagram", "per the attached spreadsheet".
2 / 5
Which sentence uses exophoric reference correctly and safely for a document that might be reformatted or have its figures reordered?
"As shown in Figure 3, latency increases with load" is the safest option. While "as shown above" (option A) is grammatically correct exophoric reference, it is fragile: if the document is reformatted, exported to PDF with different pagination, or the figure is moved, "above" may become false — the referenced content might now be below or on a different page. Referencing a labeled, numbered figure ("Figure 3") is exophoric reference that survives reformatting because the label travels with the figure regardless of its position on the page. Option C is informal and vague ("the thing before this") — unclear which specific element it refers to. Option D ("it shows") uses "it" ambiguously without establishing what "it" refers to, which could be read as either exophoric or (incorrectly) anaphoric to a nearby noun. Rule for durable technical docs: prefer numbered/labeled references ("Figure 3", "Table 2", "Appendix A") over positional ones ("above", "below", "to the left").
3 / 5
In a live screen-share during a code review, an engineer says: "See, this line right here is the problem." What makes "this" and "here" exophoric in this spoken context?
Option B is correct. In live, situated communication (screen shares, in-person pairing, pointing at a whiteboard), demonstratives like "this" and locatives like "here" are classically exophoric — they depend entirely on shared physical or visual context to resolve, not on anything stated in the discourse itself. This works fine live, but becomes a problem when the same phrasing is copy-pasted into a written record (a meeting summary, a ticket comment) without the shared screen — "this line right here" means nothing to someone reading the ticket later without the recording. Practical rule: when converting live/spoken exophoric references into permanent written records, replace them with explicit, self-contained references — "line 42 of auth.py is the problem" — so the writing works without the missing visual context.
4 / 5
A postmortem written for future readers (who won't have seen the original incident dashboard) says: "As you can see here, CPU usage spiked at 14:02." Why is this exophoric reference problematic in this specific document?
Option B is correct. Exophoric reference assumes the reader shares the writer's immediate context — but a postmortem is, by design, an artifact meant to be read later, by people (including future team members) who were never in the incident channel and never saw the live dashboard. "As you can see here" with nothing for "here" to point to in the document itself leaves the reader with no way to verify or even locate the claim. Fix: embed the actual data — "CPU usage spiked to 94% at 14:02 (see attached Grafana screenshot, Figure 2)" — converting a fragile exophoric reference into a self-contained, durable one with an embedded or numbered reference. General principle: exophoric reference is appropriate for live, synchronous communication; durable written artifacts (postmortems, RFCs, runbooks) should minimize it in favor of self-contained, labeled references.
5 / 5
Which revision of a runbook step correctly eliminates risky exophoric reference?
"Click the 'Restart Service' button in the top-right of the admin panel" is the safest, most durable phrasing. It names the specific button by its exact label and location, so it works correctly even if the runbook is reformatted, printed, converted to a different tool, or read by someone unfamiliar with the current layout of surrounding elements. "The button below" (option A) is positional exophoric reference — fragile to reformatting, similar to "as shown above" from earlier exercises. "Click here" (option C) is a classic weak exophoric/deictic reference common in poorly written UI copy and documentation — it depends entirely on "here" being visually unambiguous, which fails as soon as there are multiple clickable elements nearby. "As discussed" (option D) relies on a shared conversational context the reader may not have had access to. Runbook-writing rule: name UI elements by their exact visible label, never by position or vague deixis alone.
What will I practise in "Exophoric Reference (As Shown Above, See Figure 3) in Technical English — Grammar Exercise"?
Practise exophoric reference — as shown above, see Figure 3, click here — and when to replace fragile positional pointers with durable labeled ones. 5 exercises.
How many exercises are in this module?
This module has 5 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.