<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Writing&gt;Editing</title>	<link>http://tc.eserver.org/dir/Articles/Writing/Editing</link>
	<description>A listing of the most recently indexed works about Articles and Writing and Editing 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>Articles&gt;Writing&gt;Editing</title>
		<link>http://tc.eserver.org/dir/Articles/Writing/Editing</link>
	</image>
	<item>
		<title>What’s More Important, Content or Process?</title>
		<link>http://tc.eserver.org/35825.html</link>
		<guid>http://tc.eserver.org/35825.html</guid>
		<description>While style guidelines can be useful for maintaining consistency across a set (or several sets) of documentation, the editors that I worked with viewed the style guidelines as sacrosanct. Any deviation, no matter how small, was punishable by a nasty email and a sharply worded note to the offending writer’s manager.</description>
	</item>
	<item>
		<title>Unlocking the Special Powers of the English Language</title>
		<link>http://tc.eserver.org/35716.html</link>
		<guid>http://tc.eserver.org/35716.html</guid>
		<description>Editing really is a wonder– it’s like a multiplication of the writer’s brain, a dialogue among various copies of the author. First-draft author is an admirable workman but a bit of a hack; he writes down whatever pops into his head. Second-draft author is slower-paced but has a clearer eye for how the larger story structure fits together, or at least how it should fit once he’s done with it. Third-draft author has a remarkable knack for turning familiar and overused phrases into fresh, surprising stuff, by masticating each line. And so on. All these guys team up to make something great, and none of them could have done it alone.</description>
	</item>
	<item>
		<title>Writing Great Documentation: You Need an Editor</title>
		<link>http://tc.eserver.org/35710.html</link>
		<guid>http://tc.eserver.org/35710.html</guid>
		<description>All good writers have a dirty little secret: they’re not really that good at writing. Their editors just make it seem that way. It doesn’t matter how well you’ve mastered the language; nobody, even grammar geeks, gets this stuff right on the first pass. If you really want to produce great documentation, it needs to be edited.</description>
	</item>
	<item>
		<title>Do I Really Need a Style Guide?</title>
		<link>http://tc.eserver.org/35211.html</link>
		<guid>http://tc.eserver.org/35211.html</guid>
		<description>Style guides recommend certain styles. In the domain of technical communication, we refer to guides for writing style, presentation of content in user documentation and technical documents, and graphical user interface of software and web sites.</description>
	</item>
	<item>
		<title>More Tips for Writing Well</title>
		<link>http://tc.eserver.org/35090.html</link>
		<guid>http://tc.eserver.org/35090.html</guid>
		<description>Be vicious when you edit. Vicious. Follow these recommendations with zealous fervor. They help your writing say what it should in a way we’ll understand.</description>
	</item>
	<item>
		<title>Misplaced Modifier – Even WSJ Falls For It</title>
		<link>http://tc.eserver.org/34884.html</link>
		<guid>http://tc.eserver.org/34884.html</guid>
		<description>“Misplaced modifier” is a frequently committed logical error that even the most prominent publications fall for occasionally. Solution? Move the modifier clause right next to the subject of the sentence.</description>
	</item>
	<item>
		<title>The Construction of Author Voice by Editorial Board Members</title>
		<link>http://tc.eserver.org/34840.html</link>
		<guid>http://tc.eserver.org/34840.html</guid>
		<description>Studies of blind manuscript review have illustrated that readers often form impressions of or speculate about unknown authors&apos; identities in the manuscript review task. In this article, the authors extend that work by examining the discursive and nondiscursive features that play a role in readers&apos; active construction of author voice. Through a survey completed by 70 editorial board members of six journals in applied linguistics and rhetoric and composition, the authors identify quantitative and qualitative trends in reviewers&apos; practices regarding voice construction. Findings indicate that many readers do build impressions of an author&apos;s identity when reviewing anonymous manuscripts and that the rhetorical nature of the review task may lead readers to attend more to some discursive features than to others.</description>
	</item>
	<item>
		<title>Copywriting Tip: Have the Computer Read Your Writing Back To You</title>
		<link>http://tc.eserver.org/34746.html</link>
		<guid>http://tc.eserver.org/34746.html</guid>
		<description>You don’t have an office mate willing to read your work aloud? Don’t want to bug someone to read your two paragraph blog post? Have your computer read it to you!</description>
	</item>
	<item>
		<title>Do I Really Need a Style Guide?</title>
		<link>http://tc.eserver.org/34443.html</link>
		<guid>http://tc.eserver.org/34443.html</guid>
		<description>So, after all, I must follow those infernal style guides. I am straight-jacketed. Am I not?</description>
	</item>
	<item>
		<title>Editing and Publishing</title>
		<link>http://tc.eserver.org/34212.html</link>
		<guid>http://tc.eserver.org/34212.html</guid>
		<description>Once the main text has been written, you edit it.  Editing means breaking text into sub-documents; pointing out connections to other texts; making sure the document as a whole is in good shape; adding indices and outlines.  Editing doesn&apos;t necessarily happen after the first text has been written - I mix those stages all the time - but it deserves to be thought of as an independent discipline, because the problems it deals with are different.  Most of what people do on the World Wide Web is really editing, not writing. </description>
	</item>
	<item>
		<title>Editing Modular Documentation: Some Best Practices</title>
		<link>http://tc.eserver.org/32036.html</link>
		<guid>http://tc.eserver.org/32036.html</guid>
		<description>Much has been said about the creation of modular documentation - from content management systems, to information architecture, to delivery forms, to the usability of modular content (content being easier to use, easier to understand, and easier to find), and so on. However, not much has been said about the editing of that content, and what the editor&apos;s role is in such an environment.</description>
	</item>
	<item>
		<title>Tech Writers, Grammar, and the Prescriptive Attitude</title>
		<link>http://tc.eserver.org/32043.html</link>
		<guid>http://tc.eserver.org/32043.html</guid>
		<description>Prescriptive grammar is useful for teaching English as a second language, but it has little value for the practicing writer. Clinging to it may provide emotional security, but only at the expense of making writing harder than it needs to be. The culture-wide devotion to it will not be changed in a moment. But conscientious writers can at least change their own habits, and make life easier for themselves.</description>
	</item>
	<item>
		<title>Technical Writing&apos;s Big Secret</title>
		<link>http://tc.eserver.org/31939.html</link>
		<guid>http://tc.eserver.org/31939.html</guid>
		<description>The big secret in technical writing is that most of the harder documents aren&apos;t written by the technical writers at all. In fact, many &quot;technical writers&quot; never do any writing at all. Instead, the drafts are written by engineers or marketers. The technical writers perform editorial functions and provide publications services -- copy-editing, layout, review management, and so on.</description>
	</item>
	<item>
		<title>Good Writing and Editing: Are They Dying Arts? And, Should We Care?</title>
		<link>http://tc.eserver.org/31516.html</link>
		<guid>http://tc.eserver.org/31516.html</guid>
		<description>The answer to both questions: &quot;YES!&quot; Like us, you may be dismayed by the growing quantity of poor writing that bombards us. We see it everywhere, in publications, web sites, newspapers and corporate materials—writing that is not just full of grammatical mistakes and misused words, but is also poorly thought-out, unclear and contains downright confusing language.</description>
	</item>
	<item>
		<title>Combine Writing, Editing and Design in Your Employee Publication</title>
		<link>http://tc.eserver.org/31234.html</link>
		<guid>http://tc.eserver.org/31234.html</guid>
		<description>After more than a decade of working in the corporate environment, I have finally accepted that readers need to be enticed by more than the promise of a good read: They need proof. They want a visual two-second test-drive before they decide whether or not to spend precious minutes on a particular page.&#xD;&#xD;This is not to say that corporate readers are not discerning or that sloppy copy reads any better when dressed up with elaborate design. The truth is that in any corporate publication, a great article won&apos;t be read if the layout is poor. Similarly, a stunning design falls flat if the content doesn&apos;t live up to it.</description>
	</item>
	<item>
		<title>Final Check: Dotting Those i’s and Crossing Those t’s</title>
		<link>http://tc.eserver.org/31226.html</link>
		<guid>http://tc.eserver.org/31226.html</guid>
		<description>You’ve worked long and hard on your article, newsletter, press release, promo brochure or report. Now it’s time to move your baby off your screen and into the world. Not so long ago your baby would have gone either onto a printed page or onto the Web. These days, your words will probably head for both. Even materials such as newsletters, white papers, reports and advertorials that are first published on paper are quite likely to be reprinted, archived or otherwise reused on the Web, perhaps even as an audio file or podcast. People may even blog about your content.&#xD;&#xD;What does this mean for you as a business communicator?</description>
	</item>
	<item>
		<title>Developing Indexes</title>
		<link>http://tc.eserver.org/31098.html</link>
		<guid>http://tc.eserver.org/31098.html</guid>
		<description>As a technical writer, you&apos;ll typically have to create indexes for the print books and for online helps you develop. The type of index we mean here is the classic back-of-book index that shows page numbers on which topics and subtopics occur within the book. An online index is much the same except that you supply hypertext links rather than page numbers.</description>
	</item>
	<item>
		<title>Hockey Sticks and User Assistance: Writing in Times of Resource Constraints</title>
		<link>http://tc.eserver.org/30818.html</link>
		<guid>http://tc.eserver.org/30818.html</guid>
		<description>If you have all the resources you need, do the very best job you can in all respects. But if your resources are tight, ask yourself whether you are writing the essential stuff at a level of quality users will notice. Also, ask whether the value of the documentation you are producing aligns with the economic pressures on your company.</description>
	</item>
	<item>
		<title>Substantive Editing: Building the Logical Inner Sanctum</title>
		<link>http://tc.eserver.org/30584.html</link>
		<guid>http://tc.eserver.org/30584.html</guid>
		<description>The inner sanctum of any good piece of writing is a solid, logical core. To produce the logical core, a writer frequently has to synthesize complex information, which means understanding it well enough to transform often muddled and random detail to clear and easy to apprehend expression. Synthesis of new information, being one of the most difficult thinking skills, can require more of a writer than the writer has time for. An editor&apos;s job, from the first draft to the last, is to help build the writing around an appropriate logical core. In this workshop, participants will practice techniques that editors can use to make sure that they find, or help the writer find, the core - what users need to know, and the order in which they need to know it. Participants will form groups to scan a document, using a checklist of tips to spot problems in the document&apos;s structure. Each group will report its findings to the larger group.</description>
	</item>
	<item>
		<title>Reviewing a Peer&apos;s Work</title>
		<link>http://tc.eserver.org/30564.html</link>
		<guid>http://tc.eserver.org/30564.html</guid>
		<description>If we&apos;ve been asked by a peer to review his or her work before it is sent out to be scrutinized by the world, our job is to neither edit nor rewrite the information. Our job is to give helpful, specific feedback about where the information communicates well and where it needs work. The more we understand about how to review a peer&apos;s work effectively, and how doing this is different from editing, the better feedback we can provide.</description>
	</item>
	<item>
		<title>Editing Yourself</title>
		<link>http://tc.eserver.org/30361.html</link>
		<guid>http://tc.eserver.org/30361.html</guid>
		<description>Here are some tips that helped me edit my own writing.</description>
	</item>
	<item>
		<title>Nancy&apos;s Wordsmithy: Rules You Don&apos;t Have to Obey, Part III</title>
		<link>http://tc.eserver.org/30356.html</link>
		<guid>http://tc.eserver.org/30356.html</guid>
		<description>The funny thing is, this rule should be running out of steam, because certain standards of written English have changed in ways that make the rule at least partly obsolete. Learning it is kind of like learning to change a cloth ribbon on an old manual typewriter.</description>
	</item>
	<item>
		<title>More Than Just Error Correction: Students&apos; Perspectives on Their Revision Processes During Writing</title>
		<link>http://tc.eserver.org/29807.html</link>
		<guid>http://tc.eserver.org/29807.html</guid>
		<description>Drawing on the second phase of a 2-year study of students&apos; linguistic and compositional processes, this article describes students&apos; reflections on their online revision processes, those revisions made during the process of translating thoughts into written text. The data collected were from classroom observation and post hoc interviews with 34 students, who were observed during a writing task in the English classrooms and interviewed subsequently to elicit their reflections and understandings of their own revising processes. The analysis indicates that students tend to conceptualize revision as a macro-strategy and as a task that is predominantly undertaken as a posttextual production reviewing activity. It also indicates that students engage in multiple revising activities during writing, including many revisions that are not concerned with simple matters of surface accuracy, and many students are able to talk about these perceptively and with insight.</description>
	</item>
	<item>
		<title>Experiencing Technical Writing as Textual Coordination</title>
		<link>http://tc.eserver.org/29647.html</link>
		<guid>http://tc.eserver.org/29647.html</guid>
		<description>This paper describes a recent study of how of four technical writers managed the many artifacts (existing texts and information technologies for producing and manipulating text) that mediated their writing process. The author describes the study and characterizes several recurrent patterns of mediation, including textual reuse, remediation of information, and the staging of texts and software programs. The author describes the value of a repertoire of information technologies to technical writing and argues that technological skill should be considered a core competency of the field.</description>
	</item>
	<item>
		<title>Writing And Editing Stem Overview</title>
		<link>http://tc.eserver.org/30290.html</link>
		<guid>http://tc.eserver.org/30290.html</guid>
		<description>As part of the process of developing this overview I went back to some of the Proceedings for STC conferences that were held 10 years ago. I also reviewed issues of Technical Communication that were published at the same time.</description>
	</item>
	<item>
		<title>Writer-Editor Relationships in Revisions</title>
		<link>http://tc.eserver.org/29413.html</link>
		<guid>http://tc.eserver.org/29413.html</guid>
		<description>Editors, professional or otherwise, can be annoying individuals. The trick is to focus on the helpful parts of that annoyance and try to ignore the less-helpful parts.</description>
	</item>
	<item>
		<title>Now That You&apos;ve Got a Double Agent, What Do You Do With &apos;Em?</title>
		<link>http://tc.eserver.org/27461.html</link>
		<guid>http://tc.eserver.org/27461.html</guid>
		<description>Having demonstrated the importance of acquiring a double agent for writing projects, we now want to explain the best ways to successfully indoctrinate a double agent. This paper will help you prepare for, orient, train, and become a mentor for a double agent to help make him or her an effective member of your writing team.</description>
	</item>
	<item>
		<title>Technischer Redakteur</title>
		<link>http://tc.eserver.org/26967.html</link>
		<guid>http://tc.eserver.org/26967.html</guid>
		<description>Der Technische Redakteur erstellt und aktualisiert aussagefähige, umsetzbare, verständliche technische Dokumentationen aller Art.</description>
	</item>
	<item>
		<title>Why I Hate The Body of Your Article</title>
		<link>http://tc.eserver.org/26712.html</link>
		<guid>http://tc.eserver.org/26712.html</guid>
		<description>I really don&apos;t care what you write about. I am more interested in the format of the article, not your view or take on the subject matter.</description>
	</item>
	<item>
		<title>Why I Hate Your Article Headlines</title>
		<link>http://tc.eserver.org/26713.html</link>
		<guid>http://tc.eserver.org/26713.html</guid>
		<description>Iâ€™m a publisher for numerous sites. Hereâ€™s why I hate your headline and what you can do about it.</description>
	</item>
	<item>
		<title>Strategies for Peer-Reviewing and Team-Writing</title>
		<link>http://tc.eserver.org/25114.html</link>
		<guid>http://tc.eserver.org/25114.html</guid>
		<description>When you peer-review other people&apos;s writing, remember above all that you should consider all aspects of that writing, not just--in fact, least of all--the grammar, spelling, and punctuation.</description>
	</item>
	<item>
		<title>Editing Web Pages: A Second Look</title>
		<link>http://tc.eserver.org/24202.html</link>
		<guid>http://tc.eserver.org/24202.html</guid>
		<description>How to edit Web pages--with revision tracking--using Microsoft Word.</description>
	</item>
	<item>
		<title>The Fault of Vacuity</title>
		<link>http://tc.eserver.org/24197.html</link>
		<guid>http://tc.eserver.org/24197.html</guid>
		<description>I labeled wordiness the most obvious fault in technical writing. In retrospect, I think I was wrong. I believe the greatest fault our writing can have is vacuity, or lack of substance. We too often write words that say nothing.</description>
	</item>
	<item>
		<title>Trust Your Instincts As You Write</title>
		<link>http://tc.eserver.org/24143.html</link>
		<guid>http://tc.eserver.org/24143.html</guid>
		<description>As I write, and even after I have finished and am proofing my work, I have to be sure to be tuned in to a diminutive little editor who sits to one side of my mind.</description>
	</item>
	<item>
		<title>Editing All the Legalese the Law Allows</title>
		<link>http://tc.eserver.org/24046.html</link>
		<guid>http://tc.eserver.org/24046.html</guid>
		<description>Strictly speaking, legalese isn&apos;t intended for use outside a judicial context, but quasi-legalistic writing, with its officious tone, wordiness, and complex terms, percolates into business, government, and public interest documents. It&apos;s a parroting of the real thing -- which is already hard to swallow -- and there&apos;s a lot of it around. That kind of legalese demands to be edited, because people will do almost anything to avoid reading it.</description>
	</item>
	<item>
		<title>Beyond Gutenberg</title>
		<link>http://tc.eserver.org/24015.html</link>
		<guid>http://tc.eserver.org/24015.html</guid>
		<description>Editing must change for the Web, but perhaps not so much as you think. In paper publishing, different documents require different rules and procedures: An annual report requires more editing and more attention to detail than an office memo. Similarly, not all Web documents are equal.</description>
	</item>
	<item>
		<title>Writing Across the Curriculum</title>
		<link>http://tc.eserver.org/23334.html</link>
		<guid>http://tc.eserver.org/23334.html</guid>
		<description>The phrase &apos;writing across the curriculum&apos; is relatively new, as far as I am aware. I want to examine its underlying meaning, its various administrative forms, and its implications for the faculties of colleges and of high schools to look at the theory, the practice, and occasionally the history of the notion.</description>
	</item>
	<item>
		<title>Writing Programs and the English Department</title>
		<link>http://tc.eserver.org/23345.html</link>
		<guid>http://tc.eserver.org/23345.html</guid>
		<description>A couple of years ago John Gerber, in an article in the &lt;i&gt;ADE Bulletin,&lt;/i&gt; urged a broadened definition of &apos;literacy,&apos; one that would encompass all study relating to linguistic artifacts, from the most elementary reading and writing to the most differentiated scholarship and composing. Nearly all college English departments do include much of this broad range, but the inclusion is rarely an integration. Instead, there&apos;s the English major and the freshman composition program and the creative-writing courses and, sometimes, the courses for nonmajors: film, popular culture, folklore; business and technical writing; and so forth. In large departments different faculty members may specialize in one or another of these units, and the chairman, who is supposed to be running the whole six-ring circus, can scarcely get the different sorts to talk to one another. What integration occurs begins and ends with the yearly departmental cocktail party.</description>
	</item>
	<item>
		<title>Writer-Editor Interactions: What Works?</title>
		<link>http://tc.eserver.org/22839.html</link>
		<guid>http://tc.eserver.org/22839.html</guid>
		<description>Successful writer-editor relationships require a commitment&#xD;from both parties to teamwork, open communications, and&#xD;shared accountability for the success of each project. The&#xD;benefits from this ejj?ort include better igformation products&#xD;for users and a more congenial working environmentfor you.&#xD;Equally important, your clients will develop cor@ence and&#xD;trust when they see a project’s writer and editor combining&#xD;their skills and collaborating on shared project goals.</description>
	</item>
	<item>
		<title>Technical Translation: Craft, Not Commodity</title>
		<link>http://tc.eserver.org/22791.html</link>
		<guid>http://tc.eserver.org/22791.html</guid>
		<description>Describes the work of translators and suggests strategies buyers can use to find the best translator for their needs.</description>
	</item>
	<item>
		<title>Developing Evaluation Criteria</title>
		<link>http://tc.eserver.org/22767.html</link>
		<guid>http://tc.eserver.org/22767.html</guid>
		<description>We encourage you to adapt criteria to your specific communication assignments. You might specify, for example, the technical or scientific content for which your students are responsible. You might also specify how students will address communication concerns such as audience, purpose, context, organization, support, design, and expression.</description>
	</item>
	<item>
		<title>Incorporating Peer Review</title>
		<link>http://tc.eserver.org/22769.html</link>
		<guid>http://tc.eserver.org/22769.html</guid>
		<description>Peer review is an exercise in which students review each other&apos;s written work. Peer review is often connected to revision, a part of the writing process in which writers refine and make substantive changes to their written work.</description>
	</item>
	<item>
		<title>Incorporating Revision</title>
		<link>http://tc.eserver.org/22768.html</link>
		<guid>http://tc.eserver.org/22768.html</guid>
		<description>Revision refers to the process of reviewing one&apos;s work and making changes (either local or global) to improve the writing.  Most teachers of writing encourage students to revise their work by creating drafts and going through a process of review -- either by having teacher review drafts or having other students review drafts.</description>
	</item>
	<item>
		<title>Grammar Stammer</title>
		<link>http://tc.eserver.org/22691.html</link>
		<guid>http://tc.eserver.org/22691.html</guid>
		<description>Don&apos;t you think that it is a tragedy that 95 percent of the people who desire to be technical writers have a poor command over the language? I am sure all of us make a mistake or two, once in a while. But to make it in every sentence and paragraph shows utter disrespect for readers.</description>
	</item>
	<item>
		<title>Learning the Fine Art of Reviewing</title>
		<link>http://tc.eserver.org/22690.html</link>
		<guid>http://tc.eserver.org/22690.html</guid>
		<description>If you asked me what the most painful part of being a technical writer is, my answer would be: &apos;Getting reviews on time. Getting good feedback and inputs on your work.&apos; For me technical writing has been very pleasurable because I hardly got any review comments. My morale has therefore been very high. Project managers, developers and others are so busy trying to come up with good software (read trying to fix all the goof-ups and bugs!) that they usually tend to give documentation lesser importance. User manuals, who reads them anyway? We do not have time for it!</description>
	</item>
	<item>
		<title>One Hundred Simple Tech Writing Errors</title>
		<link>http://tc.eserver.org/22687.html</link>
		<guid>http://tc.eserver.org/22687.html</guid>
		<description>Here are the 100 writing errors that the author has encountered in his experience. (Followed by the subsequent article &apos;&lt;a href=&quot;http://tc.eserver.org/22688.html&quot;&gt;Ten More Errors in Technical Writing&lt;/a&gt;.&apos;)</description>
	</item>
	<item>
		<title>Ten More Errors in Technical Writing</title>
		<link>http://tc.eserver.org/22688.html</link>
		<guid>http://tc.eserver.org/22688.html</guid>
		<description>So, well, here are 10 more errors. This time we will focus on grammar and punctuation. Most of these are simplistic and obvious. But then they are too common. As usual, I have slipped in some content for the advanced writers too. (This article is a follow-up to &apos;&lt;a href=&quot;http://tc.eserver.org/22687.html&quot;&gt;One Hundred Simple Tech Writing Errors&#xD;&lt;/a&gt;.)</description>
	</item>
	<item>
		<title>Alternatives to the Paragraph</title>
		<link>http://tc.eserver.org/22128.html</link>
		<guid>http://tc.eserver.org/22128.html</guid>
		<description>&apos;It&apos;s all in the manual.&apos; How many times have you heard that - or said it in frustration? After all, when you are the person who wrote the manual, you know that all the answers are there. But time and again readers can&apos;t find what they need to know, or don&apos;t understand the material. Before you blame the reader, look again at how you&apos;ve presented the material.</description>
	</item>
	<item>
		<title>The Role of the Editor in the Technical Writing Team</title>
		<link>http://tc.eserver.org/22113.html</link>
		<guid>http://tc.eserver.org/22113.html</guid>
		<description>Editing today covers far more than printed materials. In this discussion, I am assuming a technical editor may be required to deal with: printed materials (for example, books, pamphlets, quick reference cards); electronic (for example, online documentation, online help, web pages); video scripts; computer-based training materials. I am also assuming that the audience for the material being edited is not comprised of other technical people; or if it is, the editor is not the person responsible for ensuring the technical accuracy of the material.</description>
	</item>
	<item>
		<title>Writing Drafts</title>
		<link>http://tc.eserver.org/21685.html</link>
		<guid>http://tc.eserver.org/21685.html</guid>
		<description>One of the keys to effective technical writing is to write, edit and re-write. Once you have completed the first draft, you will need to review it several times to  identify errors and inconsistencies in the text.</description>
	</item>
	<item>
		<title>Editing Your Own Documentation</title>
		<link>http://tc.eserver.org/21411.html</link>
		<guid>http://tc.eserver.org/21411.html</guid>
		<description>Technical writers sometimes fall into the trap of thinking that the user is stupid. I have often heard technical writers say things like &apos;well, if the user can&apos;t figure that out, maybe he’s in the wrong job!&apos;</description>
	</item>
	<item>
		<title>Writing, Editing and Designing: a Unified Process </title>
		<link>http://tc.eserver.org/20800.html</link>
		<guid>http://tc.eserver.org/20800.html</guid>
		<description>What&apos;s in it for me? That&apos;s what magazine readers must see at first glance, or they will flip on by. Winning their attention requires thoughtful blending of words and design from the beginning of the publication process.</description>
	</item>
	<item>
		<title>&quot;Prescriptive&quot; Audience Analysis: Moving Beyond the Purely Descriptive</title>
		<link>http://tc.eserver.org/20542.html</link>
		<guid>http://tc.eserver.org/20542.html</guid>
		<description>Editing and writing both require an understanding of our audience, because without that knowledge, we can&apos;t shape our words to help them easily grasp difficult concepts. To understand our audience, we do what all writers and editors do, whether consciously or unconsciously: We create an image of our audience that guides our choice of words, images, and metaphors. This image is variously known as a &apos;stereotype&apos; or a &apos;persona&apos;. Keeping that image in mind as we work helps us satisfy the reader&apos;s needs, but if we&apos;re not careful, it can also cause us to waste valuable time collecting information that doesn&apos;t really help us communicate.</description>
	</item>
	<item>
		<title>Editors: Who Needs Them?</title>
		<link>http://tc.eserver.org/20312.html</link>
		<guid>http://tc.eserver.org/20312.html</guid>
		<description>Editors can play many roles, which, as the need arises, might overlap with those of the production editor, the writer, and even the writing manager. Within the&#xD;category of editing itself, the editor can perform&#xD;different levels of edit: formatting, language, substantive.&#xD;Every pubs group needs an editor, even if only on a parttime&#xD;basis. The qualities a manager should look for in an&#xD;editor are somewhat different from those required in a&#xD;writer. Editors are less likely to have a technical&#xD;background. They must not shrink from the possibility of&#xD;confrontation, and yet must be able to give constructive&#xD;criticism in a manner that the writer will accept and&#xD;welcome.</description>
	</item>
	<item>
		<title>Editing and Revising With Flair</title>
		<link>http://tc.eserver.org/20188.html</link>
		<guid>http://tc.eserver.org/20188.html</guid>
		<description>Samuel Johnson wrote &apos;What is written without effort is&#xD;in general read without pleasure.&apos; The wisdom&#xD;contained in this pithy directive should serve as an&#xD;excellent guide for writers who edit and revise&#xD;documents to imbue them with a sense ofpanache. While&#xD;proper syntax, diction, and usage are three primary elements in the editing and revising process, other&#xD;important considerations include: (a) eliminating&#xD;redundancies; (b) avoiding jargon; (c) cleaning&#xD;bureaucratic expressions; (d) using active andpassive&#xD;voice appropriately; (e) avoiding wordiness; and Gf)&#xD;editing for slips in grammar, punctuation and&#xD;mechanics.</description>
	</item>
	<item>
		<title>Writing Shorter Manuals</title>
		<link>http://tc.eserver.org/20189.html</link>
		<guid>http://tc.eserver.org/20189.html</guid>
		<description>Large manuals are expensive to write, produce, and ship, and may make a product seem mare diflcult or complex than it really is. Shorter manuals can decrease telephone&#xD;support calls, provide a challenge to the writer, and save&#xD;time and money. With careful planning and preparation,&#xD;diJjCerent writing and design techniques, and participation&#xD;in product design, writers can shorten manuals and make&#xD;users more willing to read them.</description>
	</item>
	<item>
		<title>Writing and Editing Stem Overview</title>
		<link>http://tc.eserver.org/20129.html</link>
		<guid>http://tc.eserver.org/20129.html</guid>
		<description>What could embody this year’s theme of Evolution/Revolution more than the Writing and Editing Stem?&#xD;On the one hand, we must continue to evolve as&#xD;professionals by building our writing and editing&#xD;skills, the cornerstones of our trade. On the other, we&#xD;must stay on top of the information revolution our&#xD;industry is experiencing. This stem will help you to&#xD;do both: build upon the basics and also stay abreast&#xD;of the new technology and tools that are constantly&#xD;revolutionizing the ways we do our work.</description>
	</item>
	<item>
		<title>Writing and Editing Stem Overview</title>
		<link>http://tc.eserver.org/20067.html</link>
		<guid>http://tc.eserver.org/20067.html</guid>
		<description>The Writing and Editing Stem of the 42nd Annual STC Conference is designed to provide sessions that speak to the questions of technical&#xD;communicators today and that also remind us to &apos;stick to the basics&apos; of our craft(s). In a world of to &apos;re-imagine&apos; the audience and gain new&#xD;ever-changing technologies, we must perspectives. Find out how to motivate your accommodate both a diverse audience and a audience to learn and then keep ‘em coming back! diverse media. Our goal is to explore (proven and new) methodologies and ideas that can enhance our writing and editing skills and philosophies as we enter the 21st century.</description>
	</item>
	<item>
		<title>Can the Computer Improve your Writing Style?</title>
		<link>http://tc.eserver.org/19843.html</link>
		<guid>http://tc.eserver.org/19843.html</guid>
		<description>We have spell checkers. We have grammar checkers. What we really need is a style checker.</description>
	</item>
	<item>
		<title>Editing Tests for Writers</title>
		<link>http://tc.eserver.org/19682.html</link>
		<guid>http://tc.eserver.org/19682.html</guid>
		<description>Times are hard, and many former writers are pounding the dirt looking for work. Some who have extensive experience with peer review or revising documents are&#xD;expanding their job searches to include careers as editors. However, new editors often face a barrier to entering the profession: the editing test. Rather than taking a chance on unproven candidates, publishers and other clients typically ask&#xD;would-be editors to review short documents that test three main aspects of an editor’s skills.</description>
	</item>
	<item>
		<title>How to Edit for Content</title>
		<link>http://tc.eserver.org/19673.html</link>
		<guid>http://tc.eserver.org/19673.html</guid>
		<description>Editing involves more than just formatting and inserting page numbers. You need to ask, &apos;How can I improve the communication?&apos;&#xD;</description>
	</item>
	<item>
		<title>Technology: A Blessing for Writers and Editors?</title>
		<link>http://tc.eserver.org/19569.html</link>
		<guid>http://tc.eserver.org/19569.html</guid>
		<description>Computers have changed the way writers and editors work. But are we getting the most from the new tools?</description>
	</item>
	<item>
		<title>Writing Consistently Across Media: Ten Proofreading Tips</title>
		<link>http://tc.eserver.org/19019.html</link>
		<guid>http://tc.eserver.org/19019.html</guid>
		<description>Last time I wrote about consistency in online writing. Soon after, I received an email from Leslie Drechsler, a reader in Tustin, CA: &apos;As a Marketing Communications Specialist, I&apos;d love to hear your ideas on how to successfully implement consistency in an established business,&apos; she wrote. &apos;I thought developing a company style guide would solve the problem. But perhaps there are other ways to approach it.&#xD;&#xD;&apos;Perhaps this could be the subject of another article.&apos;&#xD;&#xD;Here&apos;s that article, Leslie. </description>
	</item>
	<item>
		<title>Electronic Outlining as a Tool for Making Writing Visible</title>
		<link>http://tc.eserver.org/18175.html</link>
		<guid>http://tc.eserver.org/18175.html</guid>
		<description>The electronic outlining software found in many commercial programs, when projected on the classroom wall, helps us train students in the main activities involved in creating an outline. Freed from paper, the electronic outline allows continuous revision, encourages multiple iterations of the many interdependent activities involved in research, planning, writing, and revision, and serves as a focal point for discussion of the ways in which the group is developing an ongoing consensus, as part of a larger conversation.</description>
	</item>
	<item>
		<title>Bug Reports: Your Road to Visibility</title>
		<link>http://tc.eserver.org/15093.html</link>
		<guid>http://tc.eserver.org/15093.html</guid>
		<description>Argues that technical writers have a professional duty to report defects in software and presents examples of software problems that require bug reports.</description>
	</item>
	<item>
		<title>Angels and Copy Editors Defend Us!</title>
		<link>http://tc.eserver.org/10022.html</link>
		<guid>http://tc.eserver.org/10022.html</guid>
		<description>Tinkering with the author&apos;s words simply because &apos;I would not write them that way&apos; is not discretion, but interference. Preserving the author&apos;s authentic voice is as important as enhancing its presentation so as to maintain the authority of the words. Of what, then, does the enhancing consist? And how does editorial discretion fit in?</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Writing/Editing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>