<?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>Technical Communication Center &#187; English</title>
	<atom:link href="http://www.technicalcommunicationcenter.com/category/english/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technicalcommunicationcenter.com</link>
	<description>Technical Writing &#38; Communication Tips, Trends &#38; Tutorials by Ugur Akinci, Ph.D.</description>
	<lastBuildDate>Fri, 30 Jul 2010 01:59:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Technical Writing &#8212; End Your Sentences with What Matters the Most</title>
		<link>http://www.technicalcommunicationcenter.com/2010/07/06/technical-writing-end-your-sentences-with-what-matters-the-most/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/07/06/technical-writing-end-your-sentences-with-what-matters-the-most/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 17:01:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Copywriting]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[Copy Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=6745</guid>
		<description><![CDATA[© 2010 Ugur Akinci Readers remember what they read the last much better than what they read first. Thus try to end your sentences with things that really matter. Don&#8217;t end your sentences with matters of secondary importance. For example, here is a sentence from U.S. OSHA Technical Manual: &#8220;Workplace investigations of ventilation systems may [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/07/06/technical-writing-end-your-sentences-with-what-matters-the-most/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Writing – How to Subordinate Your Supporting Idea to the Main Idea</title>
		<link>http://www.technicalcommunicationcenter.com/2010/07/05/technical-writing-%e2%80%93-how-to-subordinate-your-supporting-idea-to-the-main-idea/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/07/05/technical-writing-%e2%80%93-how-to-subordinate-your-supporting-idea-to-the-main-idea/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 12:54:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Copywriting]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[Copy Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=6742</guid>
		<description><![CDATA[© 2010 Ugur Akinci Some sentences in technical documents express more than one idea. One of the ideas is always the MAIN idea, expressed in the main/principal clause. The other idea SUPPORTS the main one, expressed in a subordinate clause. When constructing your sentences make sure that the readers understand the difference between those two [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/07/05/technical-writing-%e2%80%93-how-to-subordinate-your-supporting-idea-to-the-main-idea/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Writing &#8211; Combine Short Sentences to Avoid Choppy Delivery</title>
		<link>http://www.technicalcommunicationcenter.com/2010/07/03/technical-writing-combine-short-sentences-to-avoid-choppy-delivery/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/07/03/technical-writing-combine-short-sentences-to-avoid-choppy-delivery/#comments</comments>
		<pubDate>Sat, 03 Jul 2010 12:38:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=6702</guid>
		<description><![CDATA[© 2010 Ugur Akinci Most of the time you&#8217;ll hear that short is good in technical writing and long is bad. That&#8217;s true in general. But like everything else, this rule has an exception as well. If you write in too many short sentences cascading one after the other, the readers will have a hard [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/07/03/technical-writing-combine-short-sentences-to-avoid-choppy-delivery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Write Your Technical Documents with a Consistent Style Guideline</title>
		<link>http://www.technicalcommunicationcenter.com/2010/07/02/write-your-technical-documents-with-a-consistent-style-guideline/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/07/02/write-your-technical-documents-with-a-consistent-style-guideline/#comments</comments>
		<pubDate>Fri, 02 Jul 2010 13:34:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=6700</guid>
		<description><![CDATA[© 2010 Ugur Akinci A consistent technical document is one that instills confidence and trust in end-users. It all starts with a template. It doesn&#8217;t matter whether you are creating a book, help file, or a web site. A template is a must. Once you&#8217;ve got your template designed and under control, you need to [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/07/02/write-your-technical-documents-with-a-consistent-style-guideline/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mac Dictionary and Thesaurus &#8212; One of the Very Best!</title>
		<link>http://www.technicalcommunicationcenter.com/2010/07/01/mac-dictionary-and-thesaurus-one-of-the-very-best/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/07/01/mac-dictionary-and-thesaurus-one-of-the-very-best/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 18:31:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[English]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=7047</guid>
		<description><![CDATA[© 2010 Ugur Akinci I love to sing the praises of people, objects, and systems that I truly admire. That&#8217;s how I celebrate life and that&#8217;s how I really feel that&#8217;s the least I could do to express my gratitude. Here&#8217;s another such occasion: the standard Dictionary and Thesaurus that comes installed with my trusty [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/07/01/mac-dictionary-and-thesaurus-one-of-the-very-best/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Write Your Technical Documents with Consistent Tense</title>
		<link>http://www.technicalcommunicationcenter.com/2010/07/01/write-your-technical-documents-with-consistent-tense/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/07/01/write-your-technical-documents-with-consistent-tense/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 12:26:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=6693</guid>
		<description><![CDATA[© 2010 Ugur Akinci Don’t go time-traveling from one clause to another. If you have multiple clauses in a sentence, try to make sure their verbs are in the same tense. EXAMPLE: “The circuit started to overheat [PAST] when the operator shuts down the relay [SIMPLE PRESENT].” BETTER 1: The circuit started to overheat [PAST] [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/07/01/write-your-technical-documents-with-consistent-tense/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>YAHOO Style Guide to arrive on July 6th</title>
		<link>http://www.technicalcommunicationcenter.com/2010/07/01/yahoo-style-guide-to-arrive-on-july-6th/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/07/01/yahoo-style-guide-to-arrive-on-july-6th/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 11:44:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=7035</guid>
		<description><![CDATA[© 2010 Ugur Akinci YAHOO will issue its first style guide for all writers and publishers on July 6th. The style guide will help writers of all levels with shaping their writing for &#8220;online reading&#8221;, optimizing the posts for SEO and high traffic, suggesting the best ways to use apostrophes, managing a basic level of [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/07/01/yahoo-style-guide-to-arrive-on-july-6th/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Proofread your own Technical Documents</title>
		<link>http://www.technicalcommunicationcenter.com/2010/06/30/how-to-proofread-your-techncial-documents/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/06/30/how-to-proofread-your-techncial-documents/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 03:30:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Business Writing]]></category>
		<category><![CDATA[Copywriting]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[Copy Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=7031</guid>
		<description><![CDATA[by Catherine Hibbard You may have thought about taking a course on proofreader training, only to discover that it was geared towards professional proofreaders. You don&#8217;t have to be a professional proofreader to do a better job proofreading your own writing. It&#8217;s difficult to catch your own mistakes because you read what you expect to [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/06/30/how-to-proofread-your-techncial-documents/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Write Your Technical Documents in Consistent Case</title>
		<link>http://www.technicalcommunicationcenter.com/2010/06/29/write-your-technical-documents-in-consistent-case/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/06/29/write-your-technical-documents-in-consistent-case/#comments</comments>
		<pubDate>Tue, 29 Jun 2010 13:01:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=6660</guid>
		<description><![CDATA[© 2010 Ugur Akinci The verbs you use in your technical writing must agrees with the case of your subject(s). For example: The school [Main SUBJECT] where he graduated [auxiliary VERB] from is [Main VERB] the oldest in the country. (School [singular] … is [third person singular]) VIOLATION of the rule: The school where he [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/06/29/write-your-technical-documents-in-consistent-case/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Write Your Technical Documents with Consistent Voice and Mood</title>
		<link>http://www.technicalcommunicationcenter.com/2010/06/28/write-your-technical-documents-with-consistent-voice-and-mood/</link>
		<comments>http://www.technicalcommunicationcenter.com/2010/06/28/write-your-technical-documents-with-consistent-voice-and-mood/#comments</comments>
		<pubDate>Mon, 28 Jun 2010 12:55:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=6657</guid>
		<description><![CDATA[© 2010 Ugur Akinci Technical writing is consistent writing, whether you’re writing a software  or marketing specs. Your sentences need to be consistent in Voice Mood Case Tense Style If you end your sentences with the same mood, voice and tense that you start them with, the battle is already won. [Which rule did this [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2010/06/28/write-your-technical-documents-with-consistent-voice-and-mood/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
