Technical Editing Checklist
summary
A concrete checklist maps JPL’s nine edit types onto five levels of edit so teams pick depth by cost and time: run only a policy or language check when SMEs vouch for accuracy, or run full substantive and functional passes when flow and steps must be proven. Categories are explicit — language, format, functional, substantive, mechanical — and the process uses templates, style guides and cross‑reference verification; cites Judith’s Technical Editing and the original levels paper.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:30What is a Checklist
- 0:50Who is the Technical Editor
- 1:25The role of the Technical Editor
- 1:35The 9 types of edit
- 1:45Levels of edit
- 1:55Why the Checklist
- 3:00Language
- 3:20Format
related talks
27mWrite Docs Devs Love: Ten Tips To Level Up Your Tech Writing
25mTechnical Writing for Developers and Engineers
39mTackling Technical Writing
31mManaging Unmanageable Complexity
44mTesting Documentation: Why So Technical?
20mStop writing docs; Start helping
22mHow To Write Like It's Your Job
33mHow to Write Useful Technical Texts