<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Byrne, Don</title>	<link>http://tc.eserver.org/authors/Byrne,_Don</link>
	<description>A bibliography of works by Byrne, Don in the field of technical communication.</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>Byrne, Don</title>
		<link>http://tc.eserver.org/dir/Byrne,_Don</link>
	</image>
	<item>
		<title>Writing Government Policies and Procedures in Plain Language</title>
		<link>http://tc.eserver.org/30853.html</link>
		<guid>http://tc.eserver.org/30853.html</guid>
		<description>Ask ordinary citizens for an example of unreadable prose, and half of them will show you a government document; the other half will point to something written by a lawyer. As a government lawyer for more than 30 years, I wrote and reviewed safety regulations and technical policies and procedures for a major federal agency and eventually supervised other lawyers who did the same. Although I never met a technical document I didn&apos;t have the urge to rewrite, I always thought that what my fellow lawyers wrote was pretty clear. Then the plain-language movement came along, and I found I had a lot of room for improvement.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Byrne,_Don.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>