<?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>Aurora M. Brown - Social Media Specialist &#187; Common Mistakes</title>
	<atom:link href="http://www.auroramae.com/category/common-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.auroramae.com</link>
	<description>Social Media Consulting and Strategy</description>
	<lastBuildDate>Sun, 08 Feb 2009 21:03:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Today&#8217;s Troublesome Tripe: Techno-babble</title>
		<link>http://www.auroramae.com/2006/05/22/todays-troublesome-tripe-techno-babble/</link>
		<comments>http://www.auroramae.com/2006/05/22/todays-troublesome-tripe-techno-babble/#comments</comments>
		<pubDate>Tue, 23 May 2006 06:55:09 +0000</pubDate>
		<dc:creator>Aurora</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Common Mistakes]]></category>
		<category><![CDATA[Quality Websites]]></category>
		<category><![CDATA[Style & Form]]></category>
		<category><![CDATA[Website Content]]></category>
		<category><![CDATA[Writing for websites]]></category>

		<guid isPermaLink="false">http://www.auroramae.com/blog/2006/05/22/todays-troublesome-tripe-techno-babble/</guid>
		<description><![CDATA[Bad technical writing. It screams at you from every proprietary page of a comprehensive, network-enabled, specializedÂ technology and advanced application company&#8217;s website&#8230;
What?
Welcome to the land of techno-babble.Â Fraught with pitfalls, sinkholes and swamps, it is a land where heavyÂ paragraphs drag you down; sentences trip you up;Â your eyes glazeÂ over strangeÂ words; and service pages provideÂ hazy &#8220;solutions.&#8221;
Sadly, manyÂ people get lost [...]]]></description>
			<content:encoded><![CDATA[<p>Bad technical writing. It screams at you from every proprietary page of a comprehensive, network-enabled, specializedÂ technology and advanced application company&#8217;s website&#8230;</p>
<p><em>What</em>?</p>
<p>Welcome to the land of techno-babble.Â Fraught with pitfalls, sinkholes and swamps, it is a land where heavyÂ paragraphs drag you down; sentences trip you up;Â your eyes glazeÂ over strangeÂ words; and service pages provideÂ hazy &#8220;solutions.&#8221;</p>
<p>Sadly, manyÂ people get lost in this land and don&#8217;t know where to go or what to do. Give them what they really want and lead them out of confusion; tell them what you do in bold, powerful language that is simple and effective.</p>
<p>Above all else, good technical writingÂ must be <em>accessible.Â </em>Visitors should leave your site as customers, with a clear understanding ofÂ <em>what</em> your product or service <em>does</em> and what it will do for <em>them</em>.</p>
<p>Â </p>
]]></content:encoded>
			<wfw:commentRss>http://www.auroramae.com/2006/05/22/todays-troublesome-tripe-techno-babble/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Leave the Suffix -ize Alone</title>
		<link>http://www.auroramae.com/2006/05/16/leave-the-suffix-ize-alone/</link>
		<comments>http://www.auroramae.com/2006/05/16/leave-the-suffix-ize-alone/#comments</comments>
		<pubDate>Wed, 17 May 2006 06:43:57 +0000</pubDate>
		<dc:creator>Aurora</dc:creator>
				<category><![CDATA[Common Mistakes]]></category>
		<category><![CDATA[Style & Form]]></category>
		<category><![CDATA[Website Content]]></category>

		<guid isPermaLink="false">http://www.auroramae.com/blog/2006/05/16/leave-the-suffix-ize-alone/</guid>
		<description><![CDATA[A growing phenomenon in the world of words is the use of the suffix -ize. ThoughÂ it&#8217;sÂ acceptable toÂ summarize and harmonize in good taste, there&#8217;sÂ rarely, if ever,Â a reason to utilize or prioritize. Don&#8217;t smack -ize onto a noun to create a verb. ItÂ sounds worse and a better word always exists.
The word utilize is especially annoying. Use works [...]]]></description>
			<content:encoded><![CDATA[<p>A growing phenomenon in the world of words is the use of the suffix -ize. ThoughÂ it&#8217;sÂ acceptable toÂ summarize and harmonize in good taste, there&#8217;sÂ rarely, if ever,Â a reason to utilize or prioritize. Don&#8217;t smack -ize onto a noun to create a verb. ItÂ sounds worse and a better word always exists.</p>
<p>The word utilize is especially annoying. Use works as well or better, and it doesn&#8217;t convey the same coldness and sterility that characterizes the term &#8216;utilize.&#8217; The same goes for words like prioritize and finalize.</p>
<p>Using the -ize suffix to create a verbÂ immediately separates the viewer from your language. No longer is it intriguing and interestiing, but dull and hollow.Â  There are some words like harmonize and summarize that can be used sparingly, butÂ please, never, ever containerize!</p>
<p>Â </p>
]]></content:encoded>
			<wfw:commentRss>http://www.auroramae.com/2006/05/16/leave-the-suffix-ize-alone/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linking in Your Documents</title>
		<link>http://www.auroramae.com/2006/05/12/the-dos-and-donts-of-linking-in-your-documents/</link>
		<comments>http://www.auroramae.com/2006/05/12/the-dos-and-donts-of-linking-in-your-documents/#comments</comments>
		<pubDate>Fri, 12 May 2006 09:23:37 +0000</pubDate>
		<dc:creator>Aurora</dc:creator>
				<category><![CDATA[Common Mistakes]]></category>
		<category><![CDATA[Website Content]]></category>

		<guid isPermaLink="false">http://www.auroramae.com/blog/2006/05/12/the-dos-and-donts-of-linking-in-your-documents/</guid>
		<description><![CDATA[If you&#8217;re writing for the web, one of the key factors you need to be aware of is how accessible your text is to your user, otherwise known as &#8220;accessibility.&#8221; Writing should be as straightforward and intuitive as possible for your readers to ensure their continued presence on your website.
One of the worst things people [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re writing for the web, one of the key factors you need to be aware of is how accessible your text is to your user, otherwise known as &#8220;accessibility.&#8221; Writing should be as straightforward and intuitive as possible for your readers to ensure their continued presence on your website.</p>
<p>One of the worst things people do when linking to a topic is linking the descriptive words to a site without giving the actual html address.Â People like to <em>know</em> where they&#8217;re going, so do them a favor and <em>tell</em> them!Â </p>
<p>Instead of: I likeÂ <strong>Johnny Depp</strong>.</p>
<p>Give:Â I likeÂ Johnny Depp (<strong>http://www.johnnydepp.com</strong>).</p>
<p>But if the url is useless, like <strong>http://www.geocities.com/marge/imagesjd2.html</strong>,Â  linkÂ the websiteÂ to a descriptive title, such as:</p>
<p>I like Johnny Depp (<strong>Johnny DeppÂ Fan Site on Geocities.com</strong>).</p>
<p>This may not seem like a huge difference, but it is. Your users waste time trying to guess where they&#8217;re going, so make it easy on them. For more informaiton on accessibility and writing for the web, check out <u><font color="#800080"><a href="http://www.useit.com/">Jakob Nielsen&#8217;s usability website</a></font></u>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.auroramae.com/2006/05/12/the-dos-and-donts-of-linking-in-your-documents/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Period Goes BEFORE the Quotes</title>
		<link>http://www.auroramae.com/2006/05/11/period-before-quotes/</link>
		<comments>http://www.auroramae.com/2006/05/11/period-before-quotes/#comments</comments>
		<pubDate>Thu, 11 May 2006 07:54:04 +0000</pubDate>
		<dc:creator>Aurora</dc:creator>
				<category><![CDATA[Common Mistakes]]></category>
		<category><![CDATA[Grammar & Spelling]]></category>

		<guid isPermaLink="false">http://www.auroramae.com/blog/2006/05/11/period-before-quotes/</guid>
		<description><![CDATA[Only the grammophobes out there will actually care about this topic, but it is important to point out that many people evidently lack knowledge of this simple little rule: the period or comma always comes before the quotation mark.
In short: don&#8217;t write &#8220;something&#8221;. Write &#8220;something.&#8221;

While this sounds nitpicky, it shows a lack of proofreading, the [...]]]></description>
			<content:encoded><![CDATA[<p>Only the grammophobes out there will actually care about this topic, but it is important to point out that many people evidently lack knowledge of this simple little rule: the period or comma always comes before the quotation mark.</p>
<p>In short:<strong> don&#8217;t write</strong> <strong>&#8220;something&#8221;. Write &#8220;something</strong><strong>.&#8221;</strong><strong><br />
</strong></p>
<p>While this sounds nitpicky, it shows a lack of proofreading, the ultimate sign of carelessness in a professional document.</p>
<p>Common mistakes like this imply several things:</p>
<p>a) the writer doesn&#8217;t know or can&#8217;t remember their grammar.<br />
b) the writer forgot to proofread.<br />
c) the writer doesn&#8217;t care.</p>
<p>Whether you&#8217;re a writer or not, it is your responsibility to your readers to present clean, error-free material. If you don&#8217;t proofread, that implies laziness. And while lazy writing is bad enough, not caring is worse. Now some might say &#8220;well, most people aren&#8217;t that observant, so it doesn&#8217;t matter anyways.&#8221; Perhaps. But not caring does suggest a lack of respect for your own work that isn&#8217;t lost on your readers. Never underestimate your reader or client. If they&#8217;re going to read or buy something from you, they want a product or service that inspires the most confidence.</p>
<p>After all, if you don&#8217;t care about your work, why should they?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.auroramae.com/2006/05/11/period-before-quotes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Killing the Fluff</title>
		<link>http://www.auroramae.com/2006/05/10/killing-the-fluff/</link>
		<comments>http://www.auroramae.com/2006/05/10/killing-the-fluff/#comments</comments>
		<pubDate>Wed, 10 May 2006 15:08:55 +0000</pubDate>
		<dc:creator>Aurora</dc:creator>
				<category><![CDATA[Common Mistakes]]></category>
		<category><![CDATA[Style & Form]]></category>

		<guid isPermaLink="false">http://www.auroramae.com/blog/2006/05/10/killing-the-fluff/</guid>
		<description><![CDATA[A common disease that plagues most writing, â€œfluffâ€ refers to using many words to say little or nothing at all.  It is also referred to as &#8220;filler.&#8221;
Fluff is found in a lot of writing, and is especially rampant on the internet. Take a minute and read any random article, piece of copy, or content [...]]]></description>
			<content:encoded><![CDATA[<p>A common disease that plagues most writing, â€œfluffâ€ refers to using many words to say little or nothing at all.  It is also referred to as &#8220;filler.&#8221;</p>
<p>Fluff is found in a lot of writing, and is especially rampant on the internet. Take a minute and read any random article, piece of copy, or content and youâ€™ll probably notice that half the stuff youâ€™re reading doesnâ€™t actually say anything. Kind of like this post.  Annoying, huh?</p>
<p>A three hundred word article packed with good information is better than a five hundred word article that pads the information, or lack thereof, in a bunch of useless rubbish. It is about quality over quantity.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.auroramae.com/2006/05/10/killing-the-fluff/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What did you say?</title>
		<link>http://www.auroramae.com/2006/05/10/what-did-you-say/</link>
		<comments>http://www.auroramae.com/2006/05/10/what-did-you-say/#comments</comments>
		<pubDate>Wed, 10 May 2006 14:59:59 +0000</pubDate>
		<dc:creator>Aurora</dc:creator>
				<category><![CDATA[Common Mistakes]]></category>
		<category><![CDATA[Style & Form]]></category>

		<guid isPermaLink="false">http://www.auroramae.com/blog/2006/05/10/what-did-you-say/</guid>
		<description><![CDATA[Todayâ€™s topic centers on the use of overly complicated language. It is directed, of course towards the archaic musings of academic journals and the elitist drivel of snobbish websites.
Using big words and complicated prose is unnecessary and potentially alienating to your readers. In the same vein, grandiose, mellifluous sentences and excess verbiage expounding on the [...]]]></description>
			<content:encoded><![CDATA[<p>Todayâ€™s topic centers on the use of overly complicated language. It is directed, of course towards the archaic musings of academic journals and the elitist drivel of snobbish websites.</p>
<p>Using big words and complicated prose is unnecessary and potentially alienating to your readers. In the same vein, grandiose, mellifluous sentences and excess verbiage expounding on the merits of your indelibly unique product and the synergistic experience of using it are damaging to your writing and to your content.</p>
<p>This doesnâ€™t mean you canâ€™t be creative and descriptive.  Look at books like Jesusâ€™ Son or marketing geniuses like Seth Godin. Better yet, read the Clue Train Manifesto.</p>
<p>In short, avoid long words that are hard to read and harder to say. They donâ€™t make you sound more intelligent; on the contrary, they make you sound like youâ€™re trying too hard.</p>
<p>To recap: ensure your writing is clear, strong and concise. Writing that appears lofty, hokey, or over your readersâ€™ heads is sure to drive them away.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.auroramae.com/2006/05/10/what-did-you-say/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unsteady Ground</title>
		<link>http://www.auroramae.com/2006/05/10/unsteady-ground/</link>
		<comments>http://www.auroramae.com/2006/05/10/unsteady-ground/#comments</comments>
		<pubDate>Wed, 10 May 2006 14:55:40 +0000</pubDate>
		<dc:creator>Aurora</dc:creator>
				<category><![CDATA[Common Mistakes]]></category>
		<category><![CDATA[Grammar & Spelling]]></category>

		<guid isPermaLink="false">http://www.auroramae.com/blog/2006/05/10/unsteady-ground/</guid>
		<description><![CDATA[Bad grammar is yet another pitfall that is common in writing, and the internet happens to be an effective sink hole. Not only is it unpleasant to see, but it can create a feeling of carelessness that isnâ€™t lost on a reader. Bad grammar can dilute your customersâ€™ confidence in your product or service because [...]]]></description>
			<content:encoded><![CDATA[<p>Bad grammar is yet another pitfall that is common in writing, and the internet happens to be an effective sink hole. Not only is it unpleasant to see, but it can create a feeling of carelessness that isnâ€™t lost on a reader. Bad grammar can dilute your customersâ€™ confidence in your product or service because it shows a lack of professionalism.</p>
<p>Luckily, there is an easy solution to bad grammar: repetitive proofreading. For most people, once is not enough. Lather, rinse and repeat. In addition, have at least two other people proof your work for you.</p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Arial" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.auroramae.com/2006/05/10/unsteady-ground/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
