<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title> &#187; The Art of Articles</title>
	<atom:link href="http://www.newbiewriters.com/wordpress/category/articles/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newbiewriters.com/wordpress</link>
	<description></description>
	<lastBuildDate>Sat, 29 May 2010 16:18:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Proofreading Tips</title>
		<link>http://www.newbiewriters.com/wordpress/2010/05/11/proofreading-tips/</link>
		<comments>http://www.newbiewriters.com/wordpress/2010/05/11/proofreading-tips/#comments</comments>
		<pubDate>Tue, 11 May 2010 01:43:30 +0000</pubDate>
		<dc:creator>HayleyWriter</dc:creator>
				<category><![CDATA[How To Submit to Publishers]]></category>
		<category><![CDATA[Learn the Craft]]></category>
		<category><![CDATA[The Art of Articles]]></category>
		<category><![CDATA[Writing Tips]]></category>

		<guid isPermaLink="false">http://www.newbiewriters.com/wordpress/?p=202</guid>
		<description><![CDATA[Have you ever written something, sent it out to a publisher and then been horrified when you actually see it in print because of a glaring error? Sometimes, editors miss mistakes too. Whenever you write anything you intend to print, you should proofread it thoroughly yourself, before you send to a publisher.  The trouble with proofreading your own work is that you see what you expect to see, so you read what you think you wrote, and not necessarily what ...]]></description>
			<content:encoded><![CDATA[<p>Have you ever written something, sent it out to a publisher and then been horrified when you actually see it in print because of a glaring error? Sometimes, editors miss mistakes too. Whenever you write anything you intend to print, you should proofread it thoroughly yourself, before you send to a publisher.</p>
<p> The trouble with proofreading your own work is that you see what you expect to see, so you read what you think you wrote, and not necessarily what you did write. If you first and last letters of a word are in the correct order, you may not see typing errors in the middle of the word.</p>
<p>Firstly, use a good spell and grammar check. This will never pick up all of the errors, especially the words that sound the same but have different spellings for different meanings, such as there, their, and they’re. However, the spell check is a good place to start.</p>
<p>Secondly, read the work looking for the common errors you often make. If you are not sure about the meaning of particular words, use a dictionary and a thesaurus. If you commonly make mistakes in comma placement, print out the page and highlight every single comma. Re-read the comma rules one by one and check each highlighted comma on your printed document. If you can’t find a rule that explains why the comma is there, take it out. Although you can miss commas, overuse of commas is the more typical mistake to make.</p>
<p>Read your work aloud. This helps you to catch the awkward or repetitive phrases, as you tend to stumble over these passages as you read aloud.</p>
<p>Check your work for consistency. If you start spelling Summer with a capital, make sure you consistently spell it with a capital throughout the document. Don’t say 2 apples in one paragraph and three oranges in the next.</p>
<p>Finally, put your work aside for at least a couple of hours and reread it again before you send it off to the publisher. You must look at the work as if someone else has written it, not you to be a good proofreader. Assume you have made mistakes and look for them.</p>
<p>I hope this blog on proofreading articles helps. On a private note, I’m sorry I have been very quiet on this website lately – I’ve been sick and just been keeping up with the paying work. I’m getting better now, so hopefully, I’ll be more active on the forum again soon. Take care,</p>
<p>Hayley Hunkin</p>
<p>www.expandingcreationswriters.com</p>
]]></content:encoded>
			<wfw:commentRss>http://www.newbiewriters.com/wordpress/2010/05/11/proofreading-tips/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Keep it simple</title>
		<link>http://www.newbiewriters.com/wordpress/2009/12/31/keep-it-simple/</link>
		<comments>http://www.newbiewriters.com/wordpress/2009/12/31/keep-it-simple/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 15:21:26 +0000</pubDate>
		<dc:creator>Bodhi</dc:creator>
				<category><![CDATA[Learn the Craft]]></category>
		<category><![CDATA[The Art of Articles]]></category>
		<category><![CDATA[Writing Tips]]></category>

		<guid isPermaLink="false">http://www.newbiewriters.com/wordpress/?p=89</guid>
		<description><![CDATA[As an academic writer first and foremost, I have encountered several pieces of advice for how best to make my writing accessible to the layperson. Some tips are obvious, such as not using jargon. However, the best piece of advice was presented to me by a Professor on my undergraduate course, a recommendation I use not only in my non-academic writing, but also in my scientific communications: Keep it simple! Writers all too often wish to show off their intelligence by using complex ...]]></description>
			<content:encoded><![CDATA[<p>As an academic writer first and foremost, I have encountered several pieces of advice for how best to make my writing accessible to the layperson. Some tips are obvious, such as not using jargon. However, the best piece of advice was presented to me by a Professor on my undergraduate course, a recommendation I use not only in my non-academic writing, but also in my scientific communications: Keep it simple!</p>
<p>Writers all too often wish to show off their intelligence by using complex language and  assuming a certain amount of knowledge from their readers. They think that by &#8216;impressing&#8217; their reader in such a way, they will appear as superior intellects. However, all this does is alienate their audience.</p>
<p>The trick with non-fiction writing is not to make YOU appear intelligent, but to make the reader feel that THEY are intelligent. By explaining complicated matters in a simple, easy to read manner, the reader will grasp the concept and come away from the experience feeling better about themselves and you as a writer. I experience this all the time when reading certain popular science books on Quantum Physics. Pick up any book by Brian Greene, or Michio Kaku, and they will make you feel like you are an expert in the impossible. Richard Dawkins is also another excellent proponent of this method. They don&#8217;t shy away from using simpler language and concepts to portray their message.</p>
<p>A lot of writers when presented with this advice do not wish to &#8216;dumb-down&#8217; their writing; they still cling to their desire to use complex language and terminology, as they fear that not doing so will make them look like incompetent writers. They feel that they have to use long, rarely encountered words in order to demonstrate how educated and eloquent they are as writers; all they accomplish, however, is to annoy the reader, bored with constantly reaching for the dictionary.</p>
<p>So, whether you are writing fiction or non-fiction, keep it simple! Your reader will thank you.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.newbiewriters.com/wordpress/2009/12/31/keep-it-simple/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
