<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Fiend or Friend?  5 Tips for Proofreading Your Copy.</title>
	<atom:link href="http://www.topofmind.com/blog/index.php/2009/08/fiend-or-friend-5-tips-for-proofreading-your-copy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.topofmind.com/blog/index.php/2009/08/fiend-or-friend-5-tips-for-proofreading-your-copy/</link>
	<description>Mortgage CRM and Marketing Strategies</description>
	<lastBuildDate>Mon, 06 Sep 2010 19:39:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Shelley DuPont</title>
		<link>http://www.topofmind.com/blog/index.php/2009/08/fiend-or-friend-5-tips-for-proofreading-your-copy/comment-page-1/#comment-998</link>
		<dc:creator>Shelley DuPont</dc:creator>
		<pubDate>Fri, 21 Aug 2009 22:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.topofmind.com/blog/?p=1987#comment-998</guid>
		<description>I recently wrote a feature article on a businesswoman.  Every strategy that I taught my students, I applied. I read every line backwards and forwards very carefully, but I also was getting a bit strained.  I had a blogging buddy do a once over as well.  He caught some minor mechanical errors and helped me tighten up a few semantics.  The next morning before my hubby went to work, I handed it over to him. He pointed out a few more that were overlooked. Later that same day, I reread it one more time.  A little tweak here and there still needed to be done.  How embarrassing it would have been had I not had two extra set of eyes that were keen on detail.

Seldom can we see all our mistakes when writing. The lengthier the piece, the more difficult it becomes.  Another strategy I taught my students was to triple space a draft.  Space allows the eye some &quot;leg room&quot; and makes it visually easier to catch errors.

Good advice. Thanks.</description>
		<content:encoded><![CDATA[<p>I recently wrote a feature article on a businesswoman.  Every strategy that I taught my students, I applied. I read every line backwards and forwards very carefully, but I also was getting a bit strained.  I had a blogging buddy do a once over as well.  He caught some minor mechanical errors and helped me tighten up a few semantics.  The next morning before my hubby went to work, I handed it over to him. He pointed out a few more that were overlooked. Later that same day, I reread it one more time.  A little tweak here and there still needed to be done.  How embarrassing it would have been had I not had two extra set of eyes that were keen on detail.</p>
<p>Seldom can we see all our mistakes when writing. The lengthier the piece, the more difficult it becomes.  Another strategy I taught my students was to triple space a draft.  Space allows the eye some &#8220;leg room&#8221; and makes it visually easier to catch errors.</p>
<p>Good advice. Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
