<?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>blog @ spacebarpress &#187; tips</title>
	<atom:link href="http://spacebarpress.com/blog/tag/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://spacebarpress.com/blog</link>
	<description>Life as a wannabe freelance writer</description>
	<lastBuildDate>Wed, 12 May 2010 15:31:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Proofreading Tips for Technical Writers</title>
		<link>http://spacebarpress.com/blog/2009/03/proofreading-tips-for-technical-writers/</link>
		<comments>http://spacebarpress.com/blog/2009/03/proofreading-tips-for-technical-writers/#comments</comments>
		<pubDate>Thu, 12 Mar 2009 19:37:37 +0000</pubDate>
		<dc:creator>Julia</dc:creator>
				<category><![CDATA[TW]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://spacebarpress.com/blog/?p=108</guid>
		<description><![CDATA[Proofreading is an essential step in any kind of writing, but I find it&#8217;s especially important in technical writing. That&#8217;s because the information you&#8217;re trying to transmit to people must be understood immediately for a specific reason. Whether it&#8217;s the procedure on how to land a plane, or the description about the new iPhone application [...]]]></description>
			<content:encoded><![CDATA[<p>Proofreading is an essential step in any kind of writing, but I find it&#8217;s especially important in technical writing. That&#8217;s because the information you&#8217;re trying to transmit to people must be understood immediately for a specific reason. Whether it&#8217;s the procedure on how to land a plane, or the description about the new iPhone application you downloaded, it&#8217;s got to be in comprehensible. The information must be in small enough chunks that the reader can understand it and assimilate it easily.</p>
<p><span style="color: #0000ff;">This is why the words you choose to use are important. </span></p>
<p>So here are my 3 proofreading tips for any technical writer out there:</p>
<ol>
<li><strong>Read it out loud. </strong>If it sounds too complicated, it probably is.</li>
<li><strong>Let it marinate. </strong>Let your content sit for a few hours or days, if you can. Come back to it later when you haven&#8217;t been staring at it for the last 3 days.</li>
<li><strong>Get another pair of eyes on it.</strong> A fresh perspective can be helpful. This one&#8217;s a little hard for the freelancer, but you can enlist the help of friends, family members or your significant other to help out.</li>
</ol>
<p>That&#8217;s it, that&#8217;s all. Nothing too complicated or difficult about it. Three steps and your technical writing projects will be better for it. <span style="color: #0000ff;"><em>What are your proofreading tips? Do you do anything different?</em></span></p>
]]></content:encoded>
			<wfw:commentRss>http://spacebarpress.com/blog/2009/03/proofreading-tips-for-technical-writers/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
