<?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: 4 Steps to Proofreading Your Own Stuff</title>
	<atom:link href="http://myofficezilla.com/nibbles/04/4-steps-to-proof-reading-your-own-stuff/feed/" rel="self" type="application/rss+xml" />
	<link>http://myofficezilla.com/nibbles/04/4-steps-to-proof-reading-your-own-stuff/</link>
	<description>Helping you take a bite out of work!</description>
	<lastBuildDate>Wed, 19 May 2010 13:01:29 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://myofficezilla.com/nibbles/04/4-steps-to-proof-reading-your-own-stuff/comment-page-1/#comment-25</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 03 Apr 2009 19:01:31 +0000</pubDate>
		<guid isPermaLink="false">http://myofficezilla.com/nibbles/?p=180#comment-25</guid>
		<description>Oh Rita!  You should have seen the list I started with...I promised myself I&#039;d keep it to a minimum.  The list could actually go on and on.  And on.  And on.  You are spot-on regarding the consistency.  I&#039;m not sure how the reread and re-read came about.  Honestly, the proof read and proofread happened because I had it as two words in the title and changed my mind the last minute - as women tend to do! :)  I will go fix these two things right away.

Hard to believe this whole post was generated by a newsletter I received via email that utilized not one stitch of punctuation for any of the contractions it contained.  Humph!

The other two were on purpose.  You are the only one who has mentioned them though.  This leads me to believe they either go unnoticed or people see them and click away.  Frequent visitors know sassiness so maybe not...</description>
		<content:encoded><![CDATA[<p>Oh Rita!  You should have seen the list I started with&#8230;I promised myself I&#8217;d keep it to a minimum.  The list could actually go on and on.  And on.  And on.  You are spot-on regarding the consistency.  I&#8217;m not sure how the reread and re-read came about.  Honestly, the proof read and proofread happened because I had it as two words in the title and changed my mind the last minute &#8211; as women tend to do! <img src='http://myofficezilla.com/nibbles/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   I will go fix these two things right away.</p>
<p>Hard to believe this whole post was generated by a newsletter I received via email that utilized not one stitch of punctuation for any of the contractions it contained.  Humph!</p>
<p>The other two were on purpose.  You are the only one who has mentioned them though.  This leads me to believe they either go unnoticed or people see them and click away.  Frequent visitors know sassiness so maybe not&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rita M. Reali, The Persnickety Proofreader</title>
		<link>http://myofficezilla.com/nibbles/04/4-steps-to-proof-reading-your-own-stuff/comment-page-1/#comment-24</link>
		<dc:creator>Rita M. Reali, The Persnickety Proofreader</dc:creator>
		<pubDate>Fri, 03 Apr 2009 18:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://myofficezilla.com/nibbles/?p=180#comment-24</guid>
		<description>I absolutely agree with the four steps you outlined... but I must call into question the header of your first step: &quot;Read your work out load.&quot;

Did you deliberately include that gaffe (along with the use of what should have read &quot;thereof&quot;) to make your point from step two? If so, nicely done.

You hit the nail on the head with your advice to double check spellings of proper names, locations and any unfamiliar wording. By doing this, you not only ensure the correctness of your writing, but you learn information that -- if committed it to memory -- is stored there for next time you need it.

One item you didn&#039;t mention, however, is the importance of consistency within a written piece. For instance, you used &quot;proof reading&quot; as two words and one word (proofreading); you also hyphenated the word &quot;re-read&quot; in one instance and left it unhyphenated in another. Choosing a single spelling (or form) and sticking to it makes for a more unified post.

All in all, though, Sundi, a compelling and thought-provoking post. Thanks!</description>
		<content:encoded><![CDATA[<p>I absolutely agree with the four steps you outlined&#8230; but I must call into question the header of your first step: &#8220;Read your work out load.&#8221;</p>
<p>Did you deliberately include that gaffe (along with the use of what should have read &#8220;thereof&#8221;) to make your point from step two? If so, nicely done.</p>
<p>You hit the nail on the head with your advice to double check spellings of proper names, locations and any unfamiliar wording. By doing this, you not only ensure the correctness of your writing, but you learn information that &#8212; if committed it to memory &#8212; is stored there for next time you need it.</p>
<p>One item you didn&#8217;t mention, however, is the importance of consistency within a written piece. For instance, you used &#8220;proof reading&#8221; as two words and one word (proofreading); you also hyphenated the word &#8220;re-read&#8221; in one instance and left it unhyphenated in another. Choosing a single spelling (or form) and sticking to it makes for a more unified post.</p>
<p>All in all, though, Sundi, a compelling and thought-provoking post. Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
