Examples do more than decorate an explanation: they translate an abstract claim into a situation readers can evaluate, compare, and remember. In classrooms, technical manuals, and public guidance, a well-chosen case clarifies the rule before extra detail becomes necessary. A short test case exposes whether a definition is precise, because readers can check its inputs, assumptions, and outcome against the stated principle. In software documentation, a working example should show the expected format, identify the result, and reveal important limits without covering every variation. Strong explanatory writing contrasts the central case with one borderline case, making exceptions visible and showing readers and editors alike that relevance matters more than a crowded list.