Discusses grammatical arthritis (an internal buildup of rules that hinders writing flexibility); four new "rules" (concerning "data is,""none are,""hopefully," and the restrictive "which"); attitudes toward English grammar; how to be a helpful editor; and where to learn about grammar. (SR)

Argues that the greatest value of technical communicators accrue not from style book editing but from "content editing." Offers suggestions for content editing. (SR)

Makes suggestions for editing technical proposals. Discusses the marketeers, the hierarchy of hype, how to save days, managing story boards, expediting a laborious process, teaching engineers to write, writing incrementally, the art group, and the editing task. Argues that the best proposals come from starting to write early. (SR)

Suggests that editors looking for work can approach companies with some unsolicited editing of the company's own annual report. Suggest what to look for when editing an annual report. (SR)

Argues that the best approach for technical editors is to abandon the language cops' billy club, listen to what the authors want to say, and give those authors friendly expertise, without rigid prescription or blanket condemnation. (SR)

Discusses ways an editor can cut out words to help the reader understand quickly. Discusses dead wood, redundancy, redundancy in thought, smothered verbs, false precision, editing and academia, and making copy smoother. (SR)