# Filled Abbreviation Style Card

Original fictional teaching passages. Reader familiarity is a declared assumption, not a measured result. No import, jump-target, browser or human comprehension test was performed.

## Unfamiliar repeated term

Reader assumption: a person new to catalogue files does not know CSV.

Finished passage: “Copy the catalogue rows from the comma-separated values (CSV) file into your working note. Check that the CSV filename matches the catalogue named in your note.”

First use: full term followed by CSV in parentheses. Later use: CSV alone in the next sentence. Decision: introduce the repeated unfamiliar term and retain the same pairing. RFC4180 verifies this technical expansion; the copy describes an imagined task, not a performed import or data validation.

## One-use term

Reader assumption: a visitor needs to find a section in an imagined long article.

Finished passage: “Use the table of contents to find the section called Materials.”

First use: full term. Later use: none in this complete passage. Decision: retain the full wording without introducing TOC. No implemented or verified jump destination is claimed.

## Familiar abbreviation

Reader assumption: a website editor is already familiar with URL. This is a condition for the teaching choice, not research about actual editors.

Finished passage: “Record the article URL beside its title in your publication note.”

First use: URL. Later use: none in this passage. Decision: retain the assumed-familiar abbreviation with a specific action and destination for the note. Revisit the assumption for a different audience.

## Reuse for your own passage

Replace a complete passage and declare its actual intended reader. Identify the first occurrence, any later occurrence, the exact expansion if needed and the evidence or uncertainty behind a familiarity assumption. Write the final passage, then check that its first/later uses and accompanying resources agree. Inspect separately distributed sections in their own context.

Body wording choices leave the publication's heading and metadata conventions unchanged. No ranking or comprehension improvement is established.

## Primary-source scope

- Microsoft documentation house advice about audience familiarity and use pattern, checked 8 October 2026: https://learn.microsoft.com/en-us/style-guide/acronyms
- Historic Informational RFC4180, published October 2005, used only to verify the CSV expansion; later updates and varied implementations do not support an import guarantee: https://www.rfc-editor.org/rfc/rfc4180

Source advice is paraphrased. Passages and completed decisions are original teaching copy.