Pixel Girl says…

Pixel Girl Artificial Intelligence 02

Interpreted Programming Languages    Functional Programming Languages

Compiled Programming Languages    Procedural Programming Languages

Scripting Programming Languages    Mark-up Programming Languages

Logic-Based Programming Languages    Concurrent Programming Languages

Object-Oriented Programming Languages

Bender Futurama

Gretchen Bernet-Ward

Proof-reading Style Errors

IMG_20171225_204232
Breaking the proof-reading rules?

The style guide reads: Below are errors in style due to inappropriate or poor choices of language which can lead to boring, imprecise and inaccurate writing. In some situations, they may be relevant and suitable, but they are usually best avoided––

  • Clichés, over-used phrases, e.g. bed of roses, pretty as a picture.
  • Vogue words and trendy expressions, e.g. proactive, meaningful dialogue.
  • Colloquialisms in formal writing.
  • Parochialism in documents intended for a wide audience.
  • Jargon in documents intended for a general audience.
  • Euphemisms, e.g. pass away, upwardly mobile.
  • Overstatements, e.g. fabulous, incredible, fantastic, amazing.
  • Archaic words, e.g. herewith, thereby, hereinafter.
  • Sexist terms, e.g. man-made, nurseryman, waitress.
  • Tautologies, e.g. totally unique, completely empty.
  • Ambiguity, e.g. maybe I would if I could.
  • Unnecessary use of foreign words and phrases.

This information was retrieved from my older Word.doc files with no acknowledgements attached.  As a touch of humour, I wrote the short profile of Aunt Belinda.  I can only suppose such formal advice is for non-fiction writers.

Gretchen Bernet-Ward