If you’re writing a technical document, you will probably end up with a lot of lists. Lists make information easier to read, easier to scan and much less intimidating than enormous blocks of text. But once you start using lists, you quickly run into another question: How should they be

Here’s something I saw the other day: SD = V(w + 2) / 3.6 where: Note: The above formula is based on a walking speed of 1.0 m/s and provides a safety margin of 2 s. It is recommended that, at roads where there is likely to be significant use

It’s fairly easy to change a dimension halfway through a document, and then completely forget to go back and change the earlier bit. This is exactly the sort of thing a professional editor in Melbourne, or anywhere else, will spot before your readers do. Like so: All fences must be

If you’re writing a technical or educational document, chances are you’ll need to refer to official standards. As a professional editor specialising in science and technical publishing, I often see the same common issue with in-text references. Let’s say you have a whole series of official standards, all numbered for

Confusing then vs than is one of the most common grammar mistakes in English. The two words sound similar, but they have completely different meanings. Getting this right matters. Whether you’re writing an email, an essay, educational material, or a manuscript, using the correct word keeps your writing precise and

As a Melbourne based editor and accredited editor, I spend a lot of time fixing one surprisingly common issue in technical writing: Vagueness. There are some words that simply don’t belong in technical manuals, user manuals, or standard operating procedures – unless there are exceptional circumstances. Words like “may” and