Writing Style & House Style (lang-writing-style)
Language is read across the whole discipline, so its prose bar is legibility across subfields and
frameworks: a syntactician should follow a phonology paper's argument, and vice versa. The journal
also has a specific citation and formatting house style — the Language Style Sheet, closely tied to
the Unified Style Sheet for Linguistics Journals — that differs from APA, Chicago, or a subfield's
local habits. This skill polishes the writing and conforms the mechanics; it does not build the argument
(that is lang-theory-building).
When to trigger
- Polishing a draft before submission
- A reader said the paper is "only readable by [framework] people" or "buried the claim"
- Converting citations/references to Language house style
- Tightening a General Research Article toward or under the length bar
Write for the whole discipline
- Front-load the claim. By the end of the introduction the reader should know the generalization,
the analysis, its key prediction, and why a linguist outside the subfield should care.
- Gloss your jargon. Define framework-specific terms on first use; give the theory-neutral
statement of the pattern before the formal one, so the data are legible without the formalism.
- Let the numbered example carry the point. Prose should set up and interpret examples, not
restate them; refer to data by example number.
- Earn the length. A General Research Article is capped at 18,000 words and held to a stricter bar
past 12,000; cut throat-clearing, redundant derivations, and literature-for-coverage.
Language house style (verify on the Style Sheet)
- Citations: author-date, in the Unified/Language Style Sheet form — e.g., in-text
(Author 2020:145), and a reference list with the Style Sheet's punctuation and capitalization
(sentence-style article titles, full journal names, page ranges).
- Examples and glosses: numbered, Leipzig-glossed (see
lang-tables-figures).
- Terminology and symbols: consistent IPA; grammatical labels in small caps; language names and
ISO 639-3 codes where helpful.
- Notes: footnotes for substantive asides, kept lean; do not offload the argument into notes.
Conform the mechanics (checklist)
Referee-pushback patterns on prose (Language fixes)
| Referee writes… |
The Language-specific fix |
| "Impenetrable to non-[framework] readers." |
give the theory-neutral generalization first; gloss terms |
| "The contribution is buried." |
front-load the claim and prediction in the intro |
| "References not in journal style." |
convert to the Unified/Language Style Sheet form |
| "Padded / over the bar." |
cut coverage citations and redundant derivations |
Calibration (Language voice, hedged)
Reflects Language's house and readership, not universal rules; confirm wording on the Style Sheet.
The most common avoidable style failure is prose that assumes the reader already lives inside your
formalism — a general reader bounces off undefined notation. The second is mis-applied citation style
(APA/Chicago instead of the Unified/Language Style Sheet). Illustrative: a Minimalist syntax paper opens
with three pages of framework machinery before any data; the fix leads with the descriptive
generalization and a glossed example, defers the formal derivation, and reformats 60 references from APA
into Style Sheet form — the same analysis, now legible to a semanticist or a typologist.
Anti-patterns
- Prose readable only by insiders of one framework (undefined notation, no theory-neutral statement)
- Burying the claim until the discussion section
- APA/Chicago/subfield-local citation style instead of the Unified/Language Style Sheet
- Offloading the real argument into dense footnotes
- Padding to look comprehensive, pushing a General Research Article past the earned length
Output format
【Reads across subfields】claim + example legible to an outsider? [Y/N]
【Front-loaded】claim + prediction in the intro? [Y/N]
【House style】Unified/Language Style Sheet citations + refs? [Y/N]
【Glossing/IPA】examples and symbols conform? [Y/N]
【Length】within the section cap, earned? [Y/N]
【Next】lang-submission
Supplementary resources
Source: brycewang-stanford/Awesome-Journal-Skills → Language-Linguistic-Society-Skills/skills/lang-writing-style/SKILL.md
1---2name: lang-writing-style3description: Use when polishing the prose and house style of a Language (LSA) manuscript so it reads for a general linguistics audience and conforms to the Language Style Sheet / Unified Style Sheet for Linguistics. Language prizes analysis legible across frameworks and subfields; jargon and single-formalism prose lose readers. Polishes and conforms; it does not build the argument.4---567# Writing Style & House Style (lang-writing-style)89*Language* is read across the whole discipline, so its prose bar is **legibility across subfields and10frameworks**: a syntactician should follow a phonology paper's argument, and vice versa. The journal11also has a specific citation and formatting house style — the **Language Style Sheet**, closely tied to12the **Unified Style Sheet for Linguistics Journals** — that differs from APA, Chicago, or a subfield's13local habits. This skill polishes the writing and conforms the mechanics; it does not build the argument14(that is `lang-theory-building`).1516## When to trigger1718- Polishing a draft before submission19- A reader said the paper is "only readable by [framework] people" or "buried the claim"20- Converting citations/references to *Language* house style21- Tightening a General Research Article toward or under the length bar2223## Write for the whole discipline2425- **Front-load the claim.** By the end of the introduction the reader should know the generalization,26 the analysis, its key prediction, and why a linguist outside the subfield should care.27- **Gloss your jargon.** Define framework-specific terms on first use; give the theory-neutral28 statement of the pattern before the formal one, so the data are legible without the formalism.29- **Let the numbered example carry the point.** Prose should set up and interpret examples, not30 restate them; refer to data by example number.31- **Earn the length.** A General Research Article is capped at 18,000 words and held to a stricter bar32 past 12,000; cut throat-clearing, redundant derivations, and literature-for-coverage.3334## Language house style (verify on the Style Sheet)3536- **Citations:** author-date, in the **Unified/Language Style Sheet** form — e.g., in-text37 `(Author 2020:145)`, and a reference list with the Style Sheet's punctuation and capitalization38 (sentence-style article titles, full journal names, page ranges).39- **Examples and glosses:** numbered, Leipzig-glossed (see `lang-tables-figures`).40- **Terminology and symbols:** consistent IPA; grammatical labels in small caps; language names and41 ISO 639-3 codes where helpful.42- **Notes:** footnotes for substantive asides, kept lean; do not offload the argument into notes.4344## Conform the mechanics (checklist)4546- [ ] In-text citations and reference list in Unified/Language Style Sheet form (not APA/Chicago)47- [ ] Numbered examples with aligned Leipzig glosses; abbreviations listed48- [ ] Jargon defined on first use; theory-neutral statement precedes the formal one49- [ ] Claim and prediction stated in the introduction, not deferred to the conclusion50- [ ] Consistent IPA and small-caps labels; language names/codes correct51- [ ] Within the section's word limit; length earned5253## Referee-pushback patterns on prose (Language fixes)5455| Referee writes… | The Language-specific fix |56|-----------------|---------------------------|57| "Impenetrable to non-[framework] readers." | give the theory-neutral generalization first; gloss terms |58| "The contribution is buried." | front-load the claim and prediction in the intro |59| "References not in journal style." | convert to the Unified/Language Style Sheet form |60| "Padded / over the bar." | cut coverage citations and redundant derivations |6162## Calibration (Language voice, hedged)6364Reflects *Language*'s house and readership, not universal rules; confirm wording on the Style Sheet.65The most common avoidable style failure is prose that assumes the reader already lives inside your66formalism — a general reader bounces off undefined notation. The second is mis-applied citation style67(APA/Chicago instead of the Unified/Language Style Sheet). Illustrative: a Minimalist syntax paper opens68with three pages of framework machinery before any data; the fix leads with the descriptive69generalization and a glossed example, defers the formal derivation, and reformats 60 references from APA70into Style Sheet form — the same analysis, now legible to a semanticist or a typologist.7172## Anti-patterns7374- Prose readable only by insiders of one framework (undefined notation, no theory-neutral statement)75- Burying the claim until the discussion section76- APA/Chicago/subfield-local citation style instead of the Unified/Language Style Sheet77- Offloading the real argument into dense footnotes78- Padding to look comprehensive, pushing a General Research Article past the earned length7980## Output format8182```83【Reads across subfields】claim + example legible to an outsider? [Y/N]84【Front-loaded】claim + prediction in the intro? [Y/N]85【House style】Unified/Language Style Sheet citations + refs? [Y/N]86【Glossing/IPA】examples and symbols conform? [Y/N]87【Length】within the section cap, earned? [Y/N]88【Next】lang-submission89```9091## Supplementary resources9293- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reference managers, CSL styles, glossing tools94- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — Language Style Sheet / Unified Style Sheet source9596---9798**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Language-Linguistic-Society-Skills/skills/lang-writing-style/SKILL.md`
thedixitjain