TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
The discussion on typos brought this list of document priorities to mind.
This applies to technical writing in general, not just typos in resumes.
I'm curious to know the opinions of list readers to this list of document
priorities. My source is page 11 of "Creating Technical Manuals" by Gerald
Cohen and Donald H. Cunningham. These are their priorities from highest to
Filled with Specific Examples
Readable (not painful)
Specific and to the point (not overly general)
Well-paced, not dense
Uncomplicated (in writing and appearance)
Varied in sentence structure and length
Conforms to publication specifications
Cohen and Cunningham also point out that the skill and intellectual effort
required of publications people is greater for the higher priorities.