Quiz — Chapter 7: Word Choice, Tone, and Voice

Target: 70%+ before moving on. Answers and explanations are hidden — try each before expanding.

Section 1 — Multiple Choice

1. What is the difference between a word's denotation and its connotation? - a) Denotation is the spelling; connotation is the pronunciation - b) Denotation is the literal definition; connotation is the feeling, judgment, and association the word carries - c) They mean the same thing - d) Denotation is for formal writing; connotation is for casual writing

Answer **b.** *Cheap*, *inexpensive*, and *affordable* share a denotation (costs little) but differ sharply in connotation (shoddy / neutral / wise). The connotation works on the reader whether or not the writer chose it. See §7.1.

2. You're writing a blameless postmortem. Which verb best fits the tone for "the team did not monitor the queue"? - a) "neglected to monitor" — it's more vivid - b) "did not monitor" — it states the gap without the moral loading of blame - c) "failed to monitor" — it emphasizes accountability - d) "carelessly ignored" — it's honest about what happened

Answer **b.** All four are clear and arguably true, but *neglected*, *failed*, and *carelessly ignored* connote blame, which sabotages a blameless postmortem's goal of honest reporting. "Did not monitor" reports the fact without the loading. This is a connotation choice, not a clarity choice. See §7.1 and §7.10.

3. What is register? - a) The grammatical correctness of a sentence - b) The level of formality a piece adopts, set by audience and genre, expressed through word choice, contractions, and how much personality shows - c) A list of all the technical terms in a document - d) The reading level of the audience

Answer **b.** Register is appropriateness, not correctness. The same finding written for a journal (formal), a blog (neutral), and a Slack message (informal) keeps the facts and changes only the register. See §7.3.

4. Which statement about formal register is TRUE? - a) Formal writing should be bloated and full of nominalizations to sound authoritative - b) "It is important to note that a determination was made" is good formal writing - c) Formal does not mean bloated — formality lives in vocabulary and distance, but the prose should still be as clear and concise as Chapter 3 demands - d) Formal register requires the passive voice in every sentence

Answer **c.** The most common register mistake is equating formality with throat-clearing. "We determined that the catalyst was inactive" is formal *and* clean. Bloat is bad in every register. See §7.3.

5. The threshold concept of this chapter is: - a) Always use the shortest word available - b) Tone is a choice you set on purpose, not an accident that happens to your prose - c) Never use jargon - d) Hedging is always weak writing

Answer **b.** Before crossing it, you experience tone as something that "just happens"; after, you see tone and register as dials you set deliberately for the reader and the moment. See §7.3.

6. What is voice (as distinct from register)? - a) The volume at which a document should be read aloud - b) The recognizable personality and stance that persists across registers — the human behind the prose - c) Whether a sentence is active or passive - d) The font and layout of a document

Answer **b.** Register is the clothing (formality you adopt for a setting); voice is the person wearing it (the personality that survives from journal to Slack). Its enemy is faceless corporate no-voice. See §7.4.

7. Which sentence is "corporate no-voice"? - a) "We build accounting software for freelancers and try to make it boring." - b) "Our organization leverages best-in-class solutions to deliver exceptional value to stakeholders across the ecosystem." - c) "This library saves your data and gets out of your way." - d) "For three hours on Tuesday, users couldn't log in. We're sorry."

Answer **b.** It says nothing a reader could disagree with, picture, or remember — abstraction-ladder fog deployed as armor. The other three make specific, committed claims a real person could only make about a real thing. See §7.4.

8. When is hedging ("may," "suggests," "appears") the correct choice? - a) Never — hedging is always weak - b) Always — you should hedge every claim to be safe - c) When your stated certainty should match evidence that genuinely only suggests rather than proves - d) Only in casual writing

Answer **c.** Calibrated hedging is honesty about the limits of your evidence — a requirement in science, not a weakness. The sin is *empty stacked* hedging (six qualifiers on one claim) and *under-claiming* (hedging a strong result). See §7.5.

9. Why does under-claiming (writing "this may possibly suggest" when you have strong replicated evidence) count as a calibration error? - a) It doesn't — under-claiming is always safe - b) Because it wastes your evidence and makes the reader unable to tell your strong findings from your weak ones, since you hedge them all the same - c) Because short sentences are always better - d) Because passive voice is wrong

Answer **b.** Calibration cuts both ways: hedge the uncertain, commit to the certain, so the *presence* of a hedge carries information. Hedging everything flattens that signal. See §7.5.

10. Which is a weasel word/phrase? - a) "In our 1,000-query benchmark, latency dropped 34%." - b) "Studies show our approach can help to significantly improve performance in many cases." - c) "The crash is caused by a null pointer in parseConfig." - d) "Users could not log in for three hours."

Answer **b.** "Studies show" (which studies?), "can help to" (no actual improvement promised), "significantly" (undefined), "in many cases" (uncounted) — four weasels stacked. It *sounds* like a strong claim but commits to nothing checkable. The other three make committed, verifiable claims. See §7.6.

11. Which inclusive-language fix also improves precision, and why? - a) "manpower" → "manpower" (no change needed) - b) "crippled the system" → "took the system down" — the metaphor "crippled" was vague (slowed? crashed?), and the replacement names the specific failure - c) "he" → "he or she or they or one" — longer is always better - d) "use" → "utilize" — the longer word is more precise

Answer **b.** Exclusionary words are usually vague metaphors or defaults standing in for a specific meaning; the inclusive replacement names the literal thing (*took down*, *allowlist*, *staff*). Respect and precision turn out to be the same move surprisingly often. See §7.7.

12. On person-first ("person with autism") vs. identity-first ("autistic person") language, the correct guidance is: - a) Always use person-first - b) Always use identity-first - c) There is no universal rule — follow the stated preference of the community or individual, since communities genuinely differ (e.g., much of the autistic community prefers identity-first) - d) It doesn't matter; the two are interchangeable

Answer **c.** Communities disagree, sometimes sharply. Person-first is a reasonable default in clinical/formal writing when you don't know, but "default" is not "always" — asking or checking beats guessing. See §7.7.

13. When is the fancier word the right choice over the plain one? - a) Never — always use the plain word - b) When the longer word is genuinely more precise (a term of art like optimal in optimization, or methodology meaning the study of methods), not just more prestigious - c) Always — long words sound more professional - d) Only in emails

Answer **b.** Prefer the plain word *unless* the fancy one earns its keep through precision. *Utilize* is bloat for *use* 95% of the time, but *optimal* and *terminate* (in their technical senses) are precise. Swap for precision, not brevity-for-its-own-sake. See §7.8.

14. Why does technical writing reverse the English-class advice to "vary your word choice to avoid repetition"? - a) It doesn't; you should still vary terms - b) Because in technical writing, unambiguous reference matters more than texture — calling one thing a "database," then a "data store," then a "repository" makes the reader wonder whether they're the same thing - c) Because repetition is always good writing - d) Because synonyms don't exist in technical fields

Answer **b.** Elegant variation adds confusion in technical contexts. Repeat the same term for the same concept, every time — consistency is a feature, variation is a bug. Different genre, opposite rule. See §7.9.

Section 2 — True/False with Justification

State true or false and justify in one sentence.

T1. "A sentence that is perfectly clear (Chapter 3) is automatically the right word choice."

Answer **False.** A sentence can be perfectly clear and still tonally wrong — too cold, too casual, too certain for the evidence, or quietly exclusionary; clarity and word choice are partners, not the same skill. See §7.10.

T2. "Writing the same way in every genre and for every audience is a sign of authenticity."

Answer **False.** That's a failure to read the room, not authenticity; *voice* can stay constant while *register* flexes — like being the same person in a suit or in jeans. See §7.3.

T3. "Removing all hedges from a paper makes it sound more authoritative."

Answer **False.** Removing calibrated hedges makes claims *overclaim*, which a careful reader sees as ignorance of or dishonesty about the evidence's limits — destroying authority faster than any hedge; real authority is calibration. See §7.5.

T4. "Euphemisms like 'rightsizing the team' are kinder to the reader who needs to know what's happening."

Answer **False.** The soft phrase is kinder to the *writer* who doesn't want to say "layoffs"; the reader who needs the truth to make decisions is served by the straight word, and euphemism in such cases reads as evasion. See §7.6.

T5. "Informal register (Slack, internal notes) means tone doesn't matter."

Answer **False.** Informal means *casual and fast*, not *thoughtless* — a curt Slack message can damage a relationship as fast as a cold email; connotation and warmth matter in every medium. See §7.10.

T6. "Inclusive language always sacrifices precision for politeness."

Answer **False.** Most inclusive fixes *improve* precision, because the exclusionary version is usually a vague metaphor or default ("crippled" → "took down" *says which* failure); respect and precision are often the same move. See §7.7.

Section 3 — Short Answer

S1. Define connotation and give one example of two words with the same denotation but opposite connotations.

Model answer + rubric Connotation is the feeling, judgment, and association a word carries beyond its literal definition. Example: *persistent* (admirable determination) vs. *stubborn* (irrational inflexibility) — same denotation (doesn't change course), opposite feeling. **Rubric:** correct definition + a valid pair showing the feeling gap.

S2. Name the three registers and one genre that fits each.

Model answer + rubric Formal (journal article, contract, formal report), neutral (workplace email, documentation, most blog posts), informal (Slack/chat, internal notes, casual blog posts). **Rubric:** all three named with a plausible genre each.

S3. Explain the difference between an honest hedge and empty stacked hedging, with an example of each.

Model answer + rubric An honest hedge calibrates one claim to its evidence ("the data suggest a correlation" — when they suggest rather than prove). Empty stacked hedging piles qualifiers to avoid committing ("it could potentially possibly be suggested that there may be some correlation, in certain cases") — six hedges that subtract spine without adding precision. Keep the one honest hedge; cut the rest. **Rubric:** captures calibration-vs-avoidance with a valid example of each.

S4. Why does the committed, checkable claim ("latency dropped 34% in our 1,000-query benchmark") persuade more than the weaseled one ("studies show our approach can significantly help performance"), even though the weaseled one sounds bolder?

Model answer + rubric Because readers trust claims they can verify; the committed version names evidence and a number that can be checked and challenged, while the weasel borrows the *sound* of authority without supplying anything checkable — and careful readers distrust exactly that. **Rubric:** connects verifiability/commitment to trust, and names the weasel's hollowness.

S5. State, in one sentence, how word choice (this chapter) differs from clarity (Chapter 3).

Model answer + rubric Clarity *removes* the words that don't carry meaning; word choice *chooses*, among the words that would all be clear, the one whose connotation, register, certainty, and inclusivity fit this reader and genre. **Rubric:** names the remove-vs-choose distinction.

Section 4 — Applied Scenario

AS1. (Graded by rubric) Take this sentence and write it three ways — formal, neutral, informal — keeping the facts identical. Then label each register and name one marker that sets it.

Fact to convey: the new caching layer cut average page-load time from 3.2 seconds to 0.9 seconds.

Sample strong response + rubric **Formal:** *"The introduction of the caching layer reduced average page-load time from 3.2 s to 0.9 s."* (marker: no contractions, nominalized "introduction," distanced.) **Neutral:** *"After we added the caching layer, average page-load time dropped from 3.2 to 0.9 seconds."* (marker: "we," a contraction-friendly plain verb, restrained.) **Informal:** *"caching layer's live — load times went from 3.2s to 0.9s 🎉 huge."* (marker: lowercase, fragment, abbreviation, visible personality.) **Rubric (5 pts):** facts identical across all three (2) · three distinct, correctly-labeled registers (2) · a valid marker named for each (1).

AS2. (Graded by rubric) Rewrite this incident notice to remove euphemism and weasel words while keeping it humane (straight is not cruel). Then name the three dodges you removed.

"Due to an unforeseen service interruption, a subset of users may have experienced intermittent challenges accessing certain functionality during the affected window. We apologize for any inconvenience this may have caused."

Sample revision + rubric **Sample:** *"For about two hours this afternoon, users couldn't log in or place orders. The cause was a database failure, now fixed. We're sorry — this was our mistake, and we're adding monitoring so it doesn't happen again."* Dodges removed: "service interruption" (euphemism for the actual failure → named it), "a subset of users may have experienced intermittent challenges accessing certain functionality" (weasel fog → "users couldn't log in or place orders"), "the affected window" (vague → "about two hours this afternoon"). Bonus: replaced the formulaic "we apologize for any inconvenience" with a real, owned apology. **Rubric (4 pts):** named the specific failure (1) · replaced weasel fog with concrete facts (1) · stayed humane, not cruel (1) · three dodges correctly identified (1). See §7.6.

Scoring & Next Steps

Score What it means Do this
< 50% Core concepts not yet solid Re-read §7.1 (connotation), §7.3 (register), §7.5 (hedging); redo Section 1.
50–70% You know the concepts but miss edge cases Redo Exercises Part B (Revise This) and Section 2 here.
70–85% Solid — ready to proceed Move to Chapter 8 (Paragraphs). Do the Project Checkpoint (voice charter + three-register drill) first.
> 85% Strong command Try Exercises Part D/E and the "Going Deeper" hedging sidebar; you're ready to tune tone for others' writing.