The art of technical writing — or any other writing — isn’t about getting it right the first time. It’s about editing until it’s right. Here are some things I try to get my students to edit out of their reports.
Some words don’t need to be there at all. When you edit your report, see whether it might be better just to delete these.
Current/currently. The reader can see from the verb tense that this is happening now. There’s no need to point out the obvious.
etc. If you don’t want to provide an exhaustive list, start it with “such as,” “for example,” or “including.”
Needless to say/obvious/obviously. If it really is obvious or needless to say, you’ve got a whole sentence you can do without. Delete it.
In order. You can indicate the purpose just as clearly with “to”; “in order to” is superfluous.
Long-term durability. If something is durable, it will last a long time.
The process (of). This phrase may be necessary, but you’re usually better off without it. For example, “the manufacturing process” doesn’t give any more information than just “manufacturing” or “manufacture.”
Phrasing that is acceptable in casual speech and writing may not be formal enough for technical writing.
Between. You select between two choices; two people agree between themselves. If there are more than two, use “among.”
Comprise. “Comprise” means to consist of or be composed of, as in, “The United States comprises 50 states.” It’s frequently misused, as in, “The United States is comprised of 50 states.”
Data. “Data” is plural. Use the plural form of the verb.
Fewer/less. Use “fewer” with quantities that can be counted, as in “15 items or fewer” at the express checkout lane. Use “less” with bulk or aggregate amount, as in “These appliances use less electricity.”
If. “If” is a conditional, as in, “If you want to attend, please sign up by Friday.” Use “whether” to indicate two alternatives, as in, “Let me know whether you want to attend.” The implication is that you may or may not attend, and I want to know which it is.
Literal/literally. “Literal” means you’re taking the word in its most basic sense, without metaphor. Many speakers (and some writers) use “literally” when they mean “metaphorically” or “figuratively.”
Prevent. “Prevent” means to keep from occurring. You don’t prevent something before it happens; you prevent it.
Since. When used as a preposition, “since” relates to time, as in, “Since last year our costs have decreased by 10%.” If you want to show a causal connection, use “because” or “as:” “Because we made the changes, our costs have decreased by 10%.”
Acronyms and initialisms. Both are abbreviations formed from the first letters of other words. Acronyms are pronounced as words, such as “ASCII,” while initialisms are pronounced as letters, such as “FBI.” Either way, they’re a convenience for the writer. Readers, however, can take a dim view of them, especially when the text is full of them. As a writer, you need to consider what your reader will understand and what you need to explain. If your reader is familiar with a particular topic and you are simply using the standard acronyms, she’ll likely have no trouble understanding them. For less initiated readers, though, acronyms are just an annoying obstacle. Either way, you need to spell out the acronym at first use and in every figure- and table caption that uses it.
Level. “Level” (noun) means elevation or relative position on a vertical scale. You might be better off using a synonym such as “value,” “degree,” or “quantity.” “Level” (adjective) means flat, smooth, or even. “Level” (verb) means to make level or raze. Consider whether another word might be more accurate — or maybe just less stale.
Impact. The noun “impact” means collision; the verb “impact” means to strike forcefully. If no physical impact is involved, use “effect” (noun) or “affect” (verb) or a synonym such as “influence.”
Issue. As (over)used in technical writing, “issue” usually means “problem,” “challenge,” or “difficulty.” Choose one of these or another synonym that more clearly says what you mean.
I/we. Technical writing is impersonal. The emphasis is on what happened and what it means, not who did it. This is why so much technical writing uses the passive voice — it’s a way of eliminating personal pronouns. Both passive- and active voice are correct and appropriate for technical writing, although passive voice can seem rather stilted.
Upon. Use “on.”
Utilize. Just use “use.” That’s all you need.
Above/below/previously. In technical writing, particularly in a long report, it’s a courtesy to your reader to be specific about which section has the information you’re referring to. If you explained something in detail in section 5.3.1, refer the reader to section 5.3.1. Don’t just say it’s “discussed above” or “explained previously” and expect him or her to scroll through dozens of pages to find it.
Recent/recently. How long ago was “recent”? If someone reads your report five years from now, how well will “recently” have aged? If the time is important, give the year (or the specific date) when it happened.
A peculiarity of technical writing is that there is a one-to-one correspondence between a term and its meaning. In most other writing we try to take advantage of the extensive vocabulary of the English language to convey the precise nuance. By contrast, technical writing sacrifices nuance and variety for clarity.
The whole point of technical writing is to convey scientific information as clearly and accurately as possible. That requires choosing your words well and editing out anything extraneous.