<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Seattlest: Why Proofread?</title>
<link>http://seattlest.com/2007/09/14/why_proofread.php</link>
<description>All comments for Why Proofread?</description>
<language>en-us</language>
<copyright>2009 seattle_katelyn</copyright>
<lastBuildDate>Tue, 06 Jan 2009 16:00:00 -0800</lastBuildDate>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<managingEditor>kbhackett@gmail.com</managingEditor>
<webMaster>kbhackett@gmail.com</webMaster>
<ttl>60</ttl>
<item>
<title>James Callan</title>
<link>http://seattlest.com/2007/09/14/why_proofread.php#comment-1197384</link>
<guid isPermaLink="true">http://seattlest.com/2007/09/14/why_proofread.php#comment-1197384</guid>
<category>Comments</category>
<pubDate>Fri, 14 Sep 2007 21:31:49 -0800</pubDate>
<description>&lt;p&gt;&quot;Should&quot; isnt&apos; the same as &quot;must.&quot; &lt;/p&gt;</description>
</item><item>
<title>guest</title>
<link>http://seattlest.com/2007/09/14/why_proofread.php#comment-1197238</link>
<guid isPermaLink="true">http://seattlest.com/2007/09/14/why_proofread.php#comment-1197238</guid>
<category>Comments</category>
<pubDate>Fri, 14 Sep 2007 15:45:36 -0800</pubDate>
<description>&lt;p&gt;Uh, no, the comma isn&apos;t absolutely necessary.  Would&apos;ve been nice, though.

You&apos;re right that, if they meant the &quot;too&quot; as written, it doesn&apos;t make a whole lot of sense.  That doesn&apos;t make it gramatically wrong.

I highly doubt that&apos;s what was meant, but...&lt;/p&gt;</description>
</item><item>
<title>guest</title>
<link>http://seattlest.com/2007/09/14/why_proofread.php#comment-1197216</link>
<guid isPermaLink="true">http://seattlest.com/2007/09/14/why_proofread.php#comment-1197216</guid>
<category>Comments</category>
<pubDate>Fri, 14 Sep 2007 15:10:45 -0800</pubDate>
<description>&lt;p&gt;Shockingly, they got the &quot;it&apos;s&quot; right, which is one of the most common mistakes non-editors make.&lt;/p&gt;</description>
</item><item>
<title>James Callan</title>
<link>http://seattlest.com/2007/09/14/why_proofread.php#comment-1197129</link>
<guid isPermaLink="true">http://seattlest.com/2007/09/14/why_proofread.php#comment-1197129</guid>
<category>Comments</category>
<pubDate>Fri, 14 Sep 2007 13:41:54 -0800</pubDate>
<description>&lt;p&gt;I figure we can urge them to hire a designer once the get the proofreading taken care of.

And guest, if they meant &quot;too&quot; as written, they should&apos;ve used a comma before the word, and they should&apos;ve introduced someone earlier in the piece who told them to go, so that mom could tell them, too.

As is, no, it couldn&apos;t really go either way without being wrong.&lt;/p&gt;</description>
</item><item>
<title>TroyJMorris</title>
<link>http://seattlest.com/2007/09/14/why_proofread.php#comment-1197118</link>
<guid isPermaLink="true">http://seattlest.com/2007/09/14/why_proofread.php#comment-1197118</guid>
<category>Comments</category>
<pubDate>Fri, 14 Sep 2007 13:35:06 -0800</pubDate>
<description>&lt;p&gt;It&apos;s a ugly ad.

-p.s. I went to SSCC instead of Foster H.S.&lt;/p&gt;</description>
</item><item>
<title>guest</title>
<link>http://seattlest.com/2007/09/14/why_proofread.php#comment-1197106</link>
<guid isPermaLink="true">http://seattlest.com/2007/09/14/why_proofread.php#comment-1197106</guid>
<category>Comments</category>
<pubDate>Fri, 14 Sep 2007 13:25:45 -0800</pubDate>
<description>&lt;p&gt;Not sure it&apos;s necessarily the wrong &quot;to/too&quot; -- could go either way.&lt;/p&gt;</description>
</item>
</channel>
</rss>