Tag Info

New answers tagged

0

It depends on what you are trying to say. For example, concise writing is not always clear and clear language is not always concise. Saying both is in that border area between tic and idiom. For the record, you're not alone in this habit. If you read any legal writing, this repetitive style of writing is all over the place. 'Will and Testament.' 'Crimes ...


2

This doesn't seem to me like a serious problem, it's just a part of your own personal writing style. Even in technical writing, you don't necessarily want to edit all individuality out of what you produce. My advice would be only to resist the impulse to add this in places where it isn't really necessary or helpful. Personally, I like your parallelism. ...


2

Try expanding the adjectives into more fleshed-out clauses. That will keep them from being right next to each other and creating that "X and Y" structure that you're noticing, as well as allowing you the chance to more fully explore the shades of meaning that you say is your intent. "When you speak, be sure to be clear and concise." When speaking, take ...


5

When I'm editing technical documentation (and, ideally, when I'm writing it in the first place), I try to make every word earn its place. If both words in your phrases need to be there to make your point, then don't worry about it -- that's not a tic but the writing process. In the case of pairs (or larger groups) of descriptive adjectives or nouns, ...


-1

Try to focus on writing in the active tense more often. This forces you to change your entire sentence structure.


2

Here are two examples of how "e.g." has been used in scientific articles: In the first passage the authors explain who they excluded from their study. "e.g." is used to give examples of medication. Exclusion criteria included psychiatric or neurological conditions that could be associated with secondary bruxism, use of medications that may have an ...


0

Wasabi offers two approaches to it (you can find them both here) either indented root/ # entry comments can be inline after a '#' # or on their own line, also after a '#' readme.md # a child of, 'root/', it's indented # under its parent. usage.md # indented syntax is nice for small projects # and short comments. ...



Top 50 recent answers are included