---
source: https://iinventedlight.com/library/notes/plain-language-jargon-and-definitions.md
title: "Keep necessary technical terms, not jargon"
license: CC-BY-4.0
license_url: https://creativecommons.org/licenses/by/4.0/
source_license: "US government work, public domain; original synthesis in our own words"
attribution: "Summary by iinventedlight (AI-assisted). Sources: GSA / PlainLanguage.gov archive, Avoid jargon; GSA / PlainLanguage.gov archive, Minimize definitions."
author: "iinventedlight (synthesis of cited sources); text drafted with AI assistance"
date: 2026-11-05
status: published
checked_on: 2026-11-05
as_of: 2026-11-05
confidence: high
untested: "Editorial checklist only; not tested with readers. Sources fetched and evidence checked."
category: coverage-gaps
topic_area: "write-edit: technical vocabulary and local definitions"
tags: writing, plain-language, editing, jargon-and-definitions
sources:
  - id: S1
    title: "Avoid jargon"
    publisher: "GSA / PlainLanguage.gov archive"
    url: https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/words/avoid-jargon.md
    accessed: 2026-11-05
    license: "US government work, public domain"
  - id: S2
    title: "Minimize definitions"
    publisher: "GSA / PlainLanguage.gov archive"
    url: https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/words/minimize-definitions.md
    accessed: 2026-11-05
    license: "US government work, public domain"
---
# Keep necessary technical terms, not jargon

Keep technical terms when they are necessary, but remove complicated language used to impress rather than inform. [S1]
When definitions are necessary, define terms where they are used when possible. [S2]

## Checklist
1. [ ] Keep necessary technical terms; even specialist readers can misunderstand jargon. [S1]
2. [ ] Substitute everyday language where it conveys the technical information accurately. [S1]
3. [ ] Rewrite to avoid needing definitions; use as few as possible. [S2]
4. [ ] Define a word where it is used when possible; avoid a long definitions section at the document's beginning. [S2]
5. [ ] Do not define common words or words that are not used. [S2]
6. [ ] Do not assign a common word a new, specialized meaning; readers may revert to its ordinary meaning. [S2]

**Done when:** everyday language conveys the technical information accurately and clearly. [S1]

## Claims
- id: C1
  claim: Jargon adds unnecessary complexity to impress an audience.
  source: S1
  evidence: "Jargon is unnecessarily complicated language used to impress, rather than to inform, your audience."
- id: C2
  claim: Define terms locally when possible.
  source: S2
  evidence: "When possible, define a word where you use it"
- id: C3
  claim: Avoid definitions for everyday words.
  source: S2
  evidence: "Don't define common words"
- id: C4
  claim: Remove definitions for unused terms.
  source: S2
  evidence: "Don't define words you don't use"

## Sources
- [S1] Avoid jargon. GSA / PlainLanguage.gov archive. https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/words/avoid-jargon.md . License: US government work, public domain. Accessed 2026-11-05.
- [S2] Minimize definitions. GSA / PlainLanguage.gov archive. https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/words/minimize-definitions.md . License: US government work, public domain. Accessed 2026-11-05.

License: this note is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Summary by iinventedlight (AI-assisted).