<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Proofreading Your Content and Code</title>
	<atom:link href="http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/</link>
	<description>Helping you learn more and do more with WordPress</description>
	<lastBuildDate>Wed, 19 Jun 2013 03:57:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Don’t forget to proofread : Rebecca Thomas Designs</title>
		<link>http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-915307</link>
		<dc:creator><![CDATA[Don’t forget to proofread : Rebecca Thomas Designs]]></dc:creator>
		<pubDate>Mon, 26 Jan 2009 17:10:53 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-915307</guid>
		<description><![CDATA[[...] must remember to read over it (or have a trusted  acquaintance read over it for you). This goes not only for content, but code as well. The content bit makes sense. Pointless typos can just make you look silly, or even worse, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] must remember to read over it (or have a trusted  acquaintance read over it for you). This goes not only for content, but code as well. The content bit makes sense. Pointless typos can just make you look silly, or even worse, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eight Actions for Producing Quality Over Quantity &#124; LERNR.COM</title>
		<link>http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-889914</link>
		<dc:creator><![CDATA[Eight Actions for Producing Quality Over Quantity &#124; LERNR.COM]]></dc:creator>
		<pubDate>Mon, 28 Jan 2008 00:32:27 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-889914</guid>
		<description><![CDATA[[...] hit the publish post button. I need to take more time after writing to let the post sit so I can come back to read it with fresh eyes to make sure it is good and makes sense. As I wrote about in a recent post, I need to make sure the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] hit the publish post button. I need to take more time after writing to let the post sit so I can come back to read it with fresh eyes to make sure it is good and makes sense. As I wrote about in a recent post, I need to make sure the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MyScribbles: Write-ups of an Afghan</title>
		<link>http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17444</link>
		<dc:creator><![CDATA[MyScribbles: Write-ups of an Afghan]]></dc:creator>
		<pubDate>Tue, 27 Jun 2006 17:13:52 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17444</guid>
		<description><![CDATA[The way I proofread is that after having written the article, I read it at least two or three times. When I am satisfied I can come up with no further preenings, I keep it for at least  an hour or so--sometimes for a day or more. Then, after a break, I come back to it. This is very effective. I have been quite successful using this method.]]></description>
		<content:encoded><![CDATA[<p>The way I proofread is that after having written the article, I read it at least two or three times. When I am satisfied I can come up with no further preenings, I keep it for at least  an hour or so&#8211;sometimes for a day or more. Then, after a break, I come back to it. This is very effective. I have been quite successful using this method.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17237</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Mon, 26 Jun 2006 23:20:31 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17237</guid>
		<description><![CDATA[Actually, nobody knows how to spell &quot;separate&quot;. I hate &quot;seperete&quot; or &quot;seperate&quot;!

As for editing blatant typos in comments - absolutely. I hate it when I hit submit and then spot an error, so I assume others like it when I fix their boo boos. Makes them look more intelligent. But blatant errors in dumb comments I leave. Just goes to show how &quot;intelligent&quot; the commenter is. ;-)]]></description>
		<content:encoded><![CDATA[<p>Actually, nobody knows how to spell &#8220;separate&#8221;. I hate &#8220;seperete&#8221; or &#8220;seperate&#8221;!</p>
<p>As for editing blatant typos in comments &#8211; absolutely. I hate it when I hit submit and then spot an error, so I assume others like it when I fix their boo boos. Makes them look more intelligent. But blatant errors in dumb comments I leave. Just goes to show how &#8220;intelligent&#8221; the commenter is. <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Napfisk</title>
		<link>http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17222</link>
		<dc:creator><![CDATA[Napfisk]]></dc:creator>
		<pubDate>Mon, 26 Jun 2006 19:14:37 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17222</guid>
		<description><![CDATA[Apart from the code (with which I have little exeperience) I second all this. I don&#039;t have the foggiest how my English &#039;runs&#039;, stylistically speaking, but I use Word to write posts, just to make sure I don&#039;t miss anything.

Another tip that helps create distance, esp. for longer texts, is reading it backwards. Not every word of course, but chunks of sentences. They lose their coherence that way and any typos or weird formulations will stick out. Also, if these separate phrases, give you problems understanding, you can assume the whole sentence might need a full stop somewhere.

Question: do you edit blatant typos out of comments? Sometimes I do. Looks clean and it saves the commenter from mockery.

Finally, why does no one seem to be able to spell &#039;definitely&#039; right? (&#039;defiantly&#039; is one of the funniest I&#039;ve read at times.)]]></description>
		<content:encoded><![CDATA[<p>Apart from the code (with which I have little exeperience) I second all this. I don&#8217;t have the foggiest how my English &#8216;runs&#8217;, stylistically speaking, but I use Word to write posts, just to make sure I don&#8217;t miss anything.</p>
<p>Another tip that helps create distance, esp. for longer texts, is reading it backwards. Not every word of course, but chunks of sentences. They lose their coherence that way and any typos or weird formulations will stick out. Also, if these separate phrases, give you problems understanding, you can assume the whole sentence might need a full stop somewhere.</p>
<p>Question: do you edit blatant typos out of comments? Sometimes I do. Looks clean and it saves the commenter from mockery.</p>
<p>Finally, why does no one seem to be able to spell &#8216;definitely&#8217; right? (&#8216;defiantly&#8217; is one of the funniest I&#8217;ve read at times.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tammy Lenski</title>
		<link>http://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17171</link>
		<dc:creator><![CDATA[Tammy Lenski]]></dc:creator>
		<pubDate>Mon, 26 Jun 2006 12:45:50 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/06/26/proofreading-your-content-and-code/#comment-17171</guid>
		<description><![CDATA[Lorelle, to proofread articles and blog posts, I read them aloud too...to my dogs.  There&#039;s a triple benefit: I get to hear how the article sounds (and fix the messy sentences), the dogs love the attention, and I get loving and inquisitive looks, assuring me my posts much be on the verge of sheer brilliance!]]></description>
		<content:encoded><![CDATA[<p>Lorelle, to proofread articles and blog posts, I read them aloud too&#8230;to my dogs.  There&#8217;s a triple benefit: I get to hear how the article sounds (and fix the messy sentences), the dogs love the attention, and I get loving and inquisitive looks, assuring me my posts much be on the verge of sheer brilliance!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
