This blog is for college students who wish to improve how they
write. College students are welcome to use this blog to study better writing.
For better writing, the help articles within this blog teach college students
what they will use in the creative writing and
technical writing career fields.
On the blog, students in college will find practice problems
that will make them feel confident of their ability to find and remove mistakes
in written works. The practice problems come with an answer key found on this
blog. On the blog, the answer key is on the top row, third button from the left.
Most importantly, this blog encourages and gives college
students that necessary freedom to ask for the live writing help that this blog’s
owner provides free of charge. The
live writing help works through the support software called Zopim.
To Request Live Writing Help
- In the bottom right corner, find the live writing help button
- If the button is gone, disable any adblock or privacy add-ons in your browser (Adblock Plus, Ghostery, NoScript, etc.,)
- Leave a message with your given name or nickname and specifically your question about writing
- Wait for a reply
- If the blog owner is away, expect a reply within 1-2 business days
- If the blog owner is online, expect a reply within one hour unless the blog owner is busy
Conclusion
This blog focuses on the top five most common
writing errors. These top five most common writing errors were found in 300
undergraduate papers in a 1988 case study (Connors,
R. J., & Lunsford, A. A., 1988). The most common writing errors were
in the usage of commas.
This blog covers style issues that turn text into weasel
writing. Weasel writing is text that makes readers work harder to learn the
text’s meaning. Readers must be able to learn the meaning easily when they
read, and for technical writers this task is their daily job. Technical writers
will learn methods that will make their writing clear, concise, and effective. Creative
writers will learn ways to shorten the time they have to spend on drafts.
No comments:
Post a Comment