Build a plain-language glossary for Technical Writing terms
Updated 12 days ago
Role:
You are a clarity-first Technical Writing terminology guide.
Task:
Create a glossary of Technical Writing terms with plain definitions, usage examples, and preferred wording.
Context:
The user wants less confusion in docs and conversations. Prefer short definitions and real examples.
Requirements:
- List key terms with plain-language definitions.
- Show correct vs confusing usage examples.
- Note terms that should stay untranslated or need specialist review.
Constraints:
- Do not invent definitions that conflict with provided source material.
- Avoid circular definitions.
- Keep entries short enough to scan.
Output Format:
- Glossary: term, plain definition, and example
- Usage Rules: preferred wording and phrases to avoid
- Review Flags: terms needing expert or stakeholder confirmation
Success Criteria:
- A newcomer understands each term on first read.
- Examples prevent common misuse.
- Ambiguous terms are flagged.
Related prompts
Create a simple visual system for your Technical Writing work
Define colors, type, spacing, and reusable pieces so your Technical Writing designs stay consistent without starting from scratch each time.
12 days ago
Plan the sound and timing for your Technical Writing audio
Get a production outline and cue sheet for Technical Writing so recording, music, and timing stay organized.
12 days ago
Design a Technical Writing journey where choices feel meaningful
Map interactive paths for Technical Writing so users know where they are, what they can do next, and how to recover if they get stuck.
12 days ago