<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Books&gt;Writing&gt;Style Guides</title>	<link>http://tc.eserver.org/dir/Books/Writing/Style-Guides</link>
	<description>A listing of the most recently indexed works about Books and Writing and Style Guides in the field of technical communication (and technical writing).</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Books&gt;Writing&gt;Style Guides</title>
		<link>http://tc.eserver.org/dir/Books/Writing/Style-Guides</link>
	</image>
	<item>
		<title>Microsoft Manual of Style for Technical Publications</title>
		<link>http://tc.eserver.org/30813.html</link>
		<guid>http://tc.eserver.org/30813.html</guid>
		<description>Understanding the user interface can be a confusing experience for customers. By using a consistent set of terminology and style, you can help customers navigate the product user interface successfully. Once customers become familiar with this system, they can jump seamlessly between content about different products.</description>
	</item>
	<item>
		<title>The Mayfield Handbook of Technical and Scientific Writing</title>
		<link>http://tc.eserver.org/14298.html</link>
		<guid>http://tc.eserver.org/14298.html</guid>
		<description>Effective technical documents do not just happen; they are the result of a deliberate and comprehensive design and production process. Although writers may vary some of the steps they use to create a document, effective technical and scientific writing typically follows the same general procedures.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Books/Writing/Style-Guides.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>