There is nothing more sickening than a piece of writing bloated and weighed down by heavy jargon and confusing language. Call it what you will – jargoneze, legalize, bureaucrateze, or just plain gobbledygook. If you’re spreading this kind of rot, you’re a language killer and should be tried and condemned by your peers as such.

Here is a valuable resource that no technical writer, or technical-writing student, can do without: The EServer TC Library, a free library of articles on all manner of relevant subjects: I’ll also put this up on my resources page. A lot of these articles are derived from STC conferences and are available in PDF format.

When editing technical documents, how aware should you be of regional differences in pronunciation? Here is an interesting article on the subject by Brian Forte. Forte raises the following issue regarding the usage of an indefinite article with initialisms: How do you pronounce an initialism like HTML? I was taught English in public Australian schools […]