5 exercises — writing clear technical definitions using "X is a [noun] that…", "X refers to…", and "X is defined as…" in IT documentation.
0 / 5 completed
1 / 5
Which sentence uses the "X is a [noun] that…" definition structure correctly for a technical term?
Option B follows the canonical definition structure: A [term] is a [noun phrase] that [defining relative clause]. This pattern appears throughout API documentation, glossaries, and technical specifications. The noun phrase "small, independently deployable service" classifies the subject. The relative clause "that handles a single business capability" differentiates it from other services. Option A is a fragment (no main verb). Option C is grammatically broken. Option D drops the noun classifier entirely. Memorise the structure: "X is a/an [class] that [distinguishing characteristic]."
2 / 5
Which definition uses "X refers to…" correctly in technical documentation?
Option A is correct. "Refers to" introduces a noun phrase that defines the concept. The structure is: X refers to [noun phrase / definition]. Option B incorrectly uses the continuous tense "is referring" — use simple present for definitions. Option C omits the required noun phrase after "refers to" (you cannot write "refers when…"). Option D uses "a developers" — countable/uncountable error. "Refers to" is used when the term has a specific technical meaning: "Idempotency refers to the property of an operation that produces the same result regardless of how many times it is applied."
3 / 5
A glossary entry needs to define "API gateway". Which version uses "is defined as" correctly?
Option A is correct. "Is defined as" introduces a formal, precise definition and is followed by a noun phrase: "a server that acts as the single entry point…". The relative clause "that acts as…" and the participial phrase "routing them to…" add technical precision. Option B omits "is" — passive requires the auxiliary. Option C incorrectly uses "as when" — "is defined as" must be followed by a noun, not a time clause. Option D uses "and it" — a definition should not split into two coordinated clauses. Use "is defined as" in formal docs, glossaries, and API references.
4 / 5
Which sentence shows the correct use of a defining relative clause in a technical definition?
Option B uses a defining relative clause ("that distributes…") correctly. In a definition, "that" introduces a restrictive clause — essential information that distinguishes the concept. "Which" introduces a non-restrictive clause (Option A, C) — additional information, separated by commas — appropriate for description but not for the primary definition itself. Option A works as a sentence but describes a load balancer in context rather than defining it. Option D has a misplaced comma. For definitions: use "that" for the essential distinguishing property ("a server that stores static content") and reserve "which" for supplementary detail.
5 / 5
Which definition of "containerisation" is written in the most professional technical style?
Option C is the most professional definition. It uses a formal noun phrase structure ("the process of packaging…"), introduces the core term with an em dash ("— a container —"), and ends with a clear purpose clause ("that can run consistently…"). Option A uses "is when" — this structure ("X is when Y happens") is informal and grammatically imprecise; definitions should use noun phrases, not clauses. Option B is too vague. Option D uses "getting packaged" (informal gerund construction) and "and then it can run" (informal coordination). In technical writing: define with noun phrases, not "is when" or "is where".