Post History
Be clear. Write simply and plainly. Define your jargon and your acronyms, even if you think everyone knows them already, and use jargon as sparingly as you can. Imagine handing your document to so...
Answer
#4: Attribution notice removed
by
System
·
2019-12-13T11:59:56Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/2051 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T01:22:32Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/2051 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
Be clear. Write simply and plainly. Define your jargon and your acronyms, even if you think everyone knows them already, and use jargon as sparingly as you can. Imagine handing your document to someone outside your field (or better yet, try to get an editor outside your field) and aim for your work to make some kind of sense to that person. Obviously an extremely sophisticated technical paper isn't going to make complete sense to a lay person, but that person should at least be able to get the gist of what you're saying.
#1: Imported from external source
by
System
·
2011-03-17T14:39:37Z (over 13 years ago)
Original score: 6