<?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>Poke the Beehive &#187; editing</title>
	<atom:link href="http://www.pokethebeehive.com/tag/editing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pokethebeehive.com</link>
	<description>Effective writing and communication strategies for the communication-challenged</description>
	<lastBuildDate>Mon, 09 Jan 2012 18:39:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>10 Common Writing Mistakes Your Spell Checker Won&#8217;t Find</title>
		<link>http://www.pokethebeehive.com/2009/08/18/10-common-writing-mistakes-your-spell-checker-wont-find/</link>
		<comments>http://www.pokethebeehive.com/2009/08/18/10-common-writing-mistakes-your-spell-checker-wont-find/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 16:45:40 +0000</pubDate>
		<dc:creator>Dan Hutson</dc:creator>
				<category><![CDATA[general]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[spelling]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.pokethebeehive.com/?p=942</guid>
		<description><![CDATA[A few years ago writing consultant Judy Rose put together this list of common word use errors, and unfortunately it holds up very well today. If you&#8217;re one of those people who&#8217;s not sure whether it&#8217;s it&#8217;s or its, you&#8217;re or your or who&#8217;s or whose, print this one out and stick it next to [...]]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F18%2F10-common-writing-mistakes-your-spell-checker-wont-find%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F18%2F10-common-writing-mistakes-your-spell-checker-wont-find%2F&amp;source=dhutson&amp;style=compact&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><img class="alignnone size-full wp-image-944" title="Wordle" src="http://www.pokethebeehive.com/wp-content/uploads/2009/08/Wordle.jpg" alt="Wordle" width="400" height="259" /></p>
<p>A few years ago writing consultant <a href="http://jlrco.com/about_us" target="_blank">Judy Rose</a> put together <a href="http://writingenglish.wordpress.com/2006/09/18/ten-common-writing-mistakes-your-spell-checker-won%E2%80%99t-find/">this list</a> of common word use errors, and unfortunately it holds up very well today. If you&#8217;re one of those people who&#8217;s not sure whether it&#8217;s it&#8217;s or its, you&#8217;re or your or who&#8217;s or whose, print this one out and stick it next to your PC.</p>
<p>If everyone who made the errors identified in Rose&#8217;s list were to correct them, editors everywhere would breathe a huge sigh of relief.</p>
<img src="http://www.pokethebeehive.com/?ak_action=api_record_view&id=942&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.pokethebeehive.com/2009/08/18/10-common-writing-mistakes-your-spell-checker-wont-find/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Your Computer Isn&#8217;t a Typewriter</title>
		<link>http://www.pokethebeehive.com/2009/08/13/your-computer-isnt-a-typewriter/</link>
		<comments>http://www.pokethebeehive.com/2009/08/13/your-computer-isnt-a-typewriter/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 15:39:28 +0000</pubDate>
		<dc:creator>Dan Hutson</dc:creator>
				<category><![CDATA[general]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[punctuation]]></category>
		<category><![CDATA[style]]></category>
		<category><![CDATA[the mac is not a typewriter]]></category>

		<guid isPermaLink="false">http://www.pokethebeehive.com/?p=917</guid>
		<description><![CDATA[photo by valeriana solaris Guess I&#8217;m on a spelling/grammar/punctuation kick this week. I&#8217;m sure it will pass. Way back in the dark ages of the early &#8217;90s, I picked up a little book called The Mac is Not a Typewriter. Along with the dictionary, thesaurus and The Associated Press Stylebook, it has proven to be [...]]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F13%2Fyour-computer-isnt-a-typewriter%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F13%2Fyour-computer-isnt-a-typewriter%2F&amp;source=dhutson&amp;style=compact&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><img class="alignnone size-full wp-image-924" title="3626032099_9b54d3c009" src="http://www.pokethebeehive.com/wp-content/uploads/2009/08/3626032099_9b54d3c009.jpg" alt="3626032099_9b54d3c009" width="400" height="341" /></p>
<p>photo by <a href="http://www.flickr.com/photos/valerianasolaris/" target="_blank">valeriana solaris</a></p>
<p>Guess I&#8217;m on a spelling/grammar/punctuation kick this week. I&#8217;m sure it will pass.</p>
<p>Way back in the dark ages of the early &#8217;90s, I picked up a little book called <em><a href="http://www.amazon.com/gp/product/0938151312?ie=UTF8&amp;tag=pokethebeeh-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0938151312">The Mac is Not a Typewriter</a><img style="border:none !important; margin:0px !important;" src="http://www.assoc-amazon.com/e/ir?t=pokethebeeh-20&amp;l=as2&amp;o=1&amp;a=0938151312" border="0" alt="" width="1" height="1" /></em>. Along with the dictionary, thesaurus and <em><a href="http://www.amazon.com/gp/product/0465012620?ie=UTF8&amp;tag=pokethebeeh-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0465012620">The Associated Press Stylebook</a><img style="border:none !important; margin:0px !important;" src="http://www.assoc-amazon.com/e/ir?t=pokethebeeh-20&amp;l=as2&amp;o=1&amp;a=0465012620" border="0" alt="" width="1" height="1" /></em>, it has proven to be one of the more valuable reference books on my bookshelf.</p>
<p>Unfortunately it must not be on enough bookshelves. Some of the most basic lessons set forth in this guide to the rules and techniques of professional typesetting are routinely ignored by people whose occupations involve tapping at a computer keyboard eight hours a day. Here are two of my biggest pet peeves:</p>
<p><strong>One period between sentences.</strong> Seriously, do you still double-space after the period before starting a new sentence? If you learned typing on a typewriter, you might. On a typewriter the characters are monospaced, which means each takes up the same amount of space and a period requires two spaces to separate sentences. Characters on a computer are proportional, which means each takes up the amount of space appropriate for that character.</p>
<p>The one-space rule also applies to colons, semi-colons, question marks, quotations marks and any other punctuation you might be tempted to follow with two spaces.</p>
<p><strong>Use hyphens, en dashes and em dashes appropriately.</strong> I think more people get this wrong than right. There&#8217;s a reason all of these symbols are available for your use. The hyphen is used only to hyphenate a word or line break. The en dash is used between words to indicate a duration (thin space before and after). And the em dash is used to to indicate an abrupt change in thought (no spaces before or after).</p>
<p><em>The Mac is Not a Typewriter</em> has more good information than its 72 pages would suggest. You should seriously consider adding it to <em>your</em> bookshelf.</p>
<img src="http://www.pokethebeehive.com/?ak_action=api_record_view&id=917&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.pokethebeehive.com/2009/08/13/your-computer-isnt-a-typewriter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Death by a Thousand Errors</title>
		<link>http://www.pokethebeehive.com/2009/08/11/death-by-a-thousand-errors/</link>
		<comments>http://www.pokethebeehive.com/2009/08/11/death-by-a-thousand-errors/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 15:39:24 +0000</pubDate>
		<dc:creator>Dan Hutson</dc:creator>
				<category><![CDATA[general]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[punctuation]]></category>
		<category><![CDATA[spelling]]></category>

		<guid isPermaLink="false">http://www.pokethebeehive.com/?p=928</guid>
		<description><![CDATA[photo by daquella manera I&#8217;ll admit it. Anytime I see &#8220;professional&#8221; writing that includes misspelled words, bad grammar or misused punctuation, I wince. I recognize that in the new Democratic Republic of Social Media, there are those who shrug off such errors. &#8220;The important thing is that people are getting out there,&#8221; they say. &#8220;They [...]]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F11%2Fdeath-by-a-thousand-errors%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F11%2Fdeath-by-a-thousand-errors%2F&amp;source=dhutson&amp;style=compact&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><img class="alignnone size-full wp-image-933" title="2703259407_c5591577dc" src="http://www.pokethebeehive.com/wp-content/uploads/2009/08/2703259407_c5591577dc.jpg" alt="2703259407_c5591577dc" width="400" height="300" /></p>
<p>photo by <a href="http://www.flickr.com/photos/daquellamanera/" target="_blank">daquella manera</a></p>
<p>I&#8217;ll admit it. Anytime I see &#8220;professional&#8221; writing that includes misspelled words, bad grammar or misused punctuation, I wince. I recognize that in the new Democratic Republic of Social Media, there are those who shrug off such errors. &#8220;The important thing is that people are getting out there,&#8221; they say. &#8220;They shouldn&#8217;t be intimidated by their lack of writing skills.&#8221;</p>
<p>Lord knows I wouldn&#8217;t want to intimidate anyone, but &#8230; uh, no. If you didn&#8217;t master sixth-grade English class, hire someone who did. Or work to improve your own abilities. Good communication is best done by professionals. When my pipes leak, I hire an experienced plumber, not some guy who&#8217;s enthusiastic and has decided to &#8220;get out there&#8221; and do a little plumbing.</p>
<p>Sounds a bit snotty, coming from a so-called communications pro? Maybe, but consider this: Every misspelled word, misplaced comma and badly crafted sentence says something about you, whether writing is part of your job description or not. It says, &#8220;I&#8217;m not much for detail,&#8221; or, &#8220;I&#8217;m pretty casual about this quality control stuff.&#8221; Your poor writing suggests that maybe there are other things you&#8217;re a bit sloppy at. Like your plumbing.</p>
<p>It&#8217;s not just communications, of course. Everything you do says something about your work ethic, organizational culture, quality of service, etc. Your brand grows out of every point of contact you have with your stakeholders or customers.When I see your poor communication, I wonder what else you&#8217;re not so great at. And that should worry you.</p>
<img src="http://www.pokethebeehive.com/?ak_action=api_record_view&id=928&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.pokethebeehive.com/2009/08/11/death-by-a-thousand-errors/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>10 Top Tweets in July</title>
		<link>http://www.pokethebeehive.com/2009/08/04/10-top-tweets-in-july/</link>
		<comments>http://www.pokethebeehive.com/2009/08/04/10-top-tweets-in-july/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 15:16:13 +0000</pubDate>
		<dc:creator>Dan Hutson</dc:creator>
				<category><![CDATA[general]]></category>
		<category><![CDATA[brain traffic]]></category>
		<category><![CDATA[cannes lions international advertising festival]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[david letterman]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[elevator pitch]]></category>
		<category><![CDATA[haro]]></category>
		<category><![CDATA[internal communications]]></category>
		<category><![CDATA[kevin spacey]]></category>
		<category><![CDATA[kivi leroux miller]]></category>
		<category><![CDATA[kristina halvorson]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[medical school]]></category>
		<category><![CDATA[nonprofit]]></category>
		<category><![CDATA[nursing]]></category>
		<category><![CDATA[peter shankman]]></category>
		<category><![CDATA[social media]]></category>
		<category><![CDATA[social networking]]></category>
		<category><![CDATA[storytelling]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[wild apricot]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.pokethebeehive.com/?p=865</guid>
		<description><![CDATA[photo by wildxplorer Time once again for a quick roundup of the 10 most popular links I tweeted last month. Twitter continues to be a fixation for many of us, but there also was lots of interest in storytelling, internal communication and social media in general. In order of popularity: Advice From the Pros: Telling [...]]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F04%2F10-top-tweets-in-july%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F08%2F04%2F10-top-tweets-in-july%2F&amp;source=dhutson&amp;style=compact&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><img class="alignnone size-full wp-image-869" title="2124139051_d512650237_b" src="http://www.pokethebeehive.com/wp-content/uploads/2009/08/2124139051_d512650237_b.jpg" alt="2124139051_d512650237_b" /></p>
<p>photo by <a href="http://www.flickr.com/photos/krayker/" target="_blank">wildxplorer</a></p>
<p>Time once again for a quick roundup of the 10 most popular links I tweeted last month. Twitter continues to be a fixation for many of us, but there also was lots of interest in storytelling, internal communication and social media in general. In order of popularity:</p>
<p><a href="http://bit.ly/dhUaX" target="_blank">Advice From the Pros: Telling It Like It Is</a> courtesy of Brain Traffic, noted content strategist <a id="aptureLink_I8m7EYrWBJ" href="http://twitter.com/halvorson">Kristina Halvorson</a>&#8216;s firm, preaches the gospel of short, sweet and simple (my kind of sermon).</p>
<p><a href="http://bit.ly/El4PM" target="_blank">Content Creation Strategy for Nonprofits</a> is a slide deck from <a href="http://twitter.com/kivilm" target="_blank">Kivi Leroux Miller</a> on how you can effectively manage all the content you create in support of your marketing and communication efforts.</p>
<p><a id="aptureLink_mhsS6dcbVt" href="http://twitter.com/skydiver">Peter Shankman</a>, the man behind <a href="http://www.helpareporter.com/" target="_blank">HARO</a>, asks the eternal question, <a href="http://bit.ly/qAYWp" target="_blank">Is Your Social Media Expert Really an Expert? </a></p>
<p><a href="http://bit.ly/15Z0cV" target="_blank">Time for a Twitter Reality Check</a>, courtesy of yours truly, takes a look at the reality behind the hype that is Twitter (and I&#8217;ll be reviewing some of the feedback I received in my next post).</p>
<p><a href="http://bit.ly/RG8Ru" target="_blank">6 Lessons From the Best Marketing Campaign Ever</a> looks at how an unlikely underdog stunned the marketing world at the <a href="http://www.canneslions.com/about/" target="_blank">Cannes Lions International Advertising Festival</a>.</p>
<p><a href="http://www.wildapricot.com/blogs/newsblog/default.aspx" target="_blank">Wild Apricot</a> did us all a real service in compiling <a href="http://bit.ly/bbQDn" target="_blank">Social Media for Nonprofits: 26 Presentations</a>. Now there&#8217;s no excuse for not being ready to explain this stuff to your organization.</p>
<p><a href="http://bit.ly/miVAr" target="_blank">Kevin Spacey Explains Twitter to Letterman</a> pretty much sums it up. Watch it. It&#8217;s funny stuff.</p>
<p><a href="http://bit.ly/qGrcA" target="_blank">Use of Social Networking Tools Growing in Nursing, Medical Schools</a> looks at a new study that finds growing popularity of Web 2.0 tools in health curricula.</p>
<p><a href="http://bit.ly/zo16Q" target="_blank">How to Tell Your Story in 100 Words or Less</a> is my take on the value we all can derive from having an elevator pitch.</p>
<p><a href="http://bit.ly/uyiUF" target="_blank">Internal Communications and Twitter</a> is me again on how Twitter might be used to support an effective internal communications program.</p>
<p>That&#8217;s it for July&#8217;s tweets. I&#8217;m out there every day in search of useful info on communications, marketing, social media and more, so be sure to <a href="http://twitter.com/dhutson" target="_blank">follow me</a> on Twitter so you don&#8217;t miss the good stuff.</p>
<img src="http://www.pokethebeehive.com/?ak_action=api_record_view&id=865&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.pokethebeehive.com/2009/08/04/10-top-tweets-in-july/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Writing Emails People Will Actually Read</title>
		<link>http://www.pokethebeehive.com/2009/05/07/writing-emails-people-will-actually-read/</link>
		<comments>http://www.pokethebeehive.com/2009/05/07/writing-emails-people-will-actually-read/#comments</comments>
		<pubDate>Thu, 07 May 2009 14:00:19 +0000</pubDate>
		<dc:creator>Dan Hutson</dc:creator>
				<category><![CDATA[general]]></category>
		<category><![CDATA[david silverman]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.pokethebeehive.com/?p=416</guid>
		<description><![CDATA[photo by psd Despite the persistent predictions that email is not long for this world, those of us who actually live in this world continue to be plagued by it. So until the bell finally tolls for e, we all need to do a better job of writing emails people will actually read. David Silverman [...]]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F05%2F07%2Fwriting-emails-people-will-actually-read%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.pokethebeehive.com%2F2009%2F05%2F07%2Fwriting-emails-people-will-actually-read%2F&amp;source=dhutson&amp;style=compact&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://www.pokethebeehive.com/wp-content/uploads/2009/05/110109112_bf11472589.jpg"><img class="alignnone size-full wp-image-417" title="110109112_bf11472589" src="http://www.pokethebeehive.com/wp-content/uploads/2009/05/110109112_bf11472589.jpg" alt="110109112_bf11472589" width="450" height="329" /></a></p>
<p>photo by <a href="http://www.flickr.com/photos/psd/" target="_blank">psd</a></p>
<p>Despite the<a href="http://www.websocialarchitecture.com/community/2009/03/death-of-email-not-a-minute-too-soon.html" target="_blank"> persistent predictions that email is not long for this world</a>, those of us who actually live in this world continue to be plagued by it. So until the bell finally tolls for e, we all need to do a better job of writing emails people will actually read.</p>
<p><span class="zem_slink">David Silverman</span> recently wrote that the average email requires anywhere from two to 50 revisions (depending on the audience) before it&#8217;s ready for dissemination. In theory it may sound reasonable to expect someone to edit an email 40 or 50 times when it&#8217;s going out to thousands of employees, but I guarantee you it doesn&#8217;t happen with most emails in most organizations.</p>
<p>That said, Silverman does share a great checklist to consider when making those theoretical revisions. You&#8217;ll find it <a href="http://blogs.harvardbusiness.org/silverman/2009/04/how-to-revise-an-email-so-that.html?cm_mmc=npv-_-WEEKLY_HOTLIST-_-APR_2009-_-HOTLIST0417" target="_blank">here</a>. This is another one to print out and stick near your computer.</p>
<div class="zemanta-pixie" style="margin-top: 10px; height: 15px;"><a class="zemanta-pixie-a" title="Reblog this post [with Zemanta]" href="http://reblog.zemanta.com/zemified/30ec335a-8d08-4c6a-8d75-87813186c255/"><img class="zemanta-pixie-img" style="border: medium none; float: right;" src="http://img.zemanta.com/reblog_e.png?x-id=30ec335a-8d08-4c6a-8d75-87813186c255" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
<img src="http://www.pokethebeehive.com/?ak_action=api_record_view&id=416&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.pokethebeehive.com/2009/05/07/writing-emails-people-will-actually-read/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

