<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
categoryallspace2-Grammar
<channel>
	<title>Grammar</title>	<link>http://tc.eserver.org/dir/Grammar</link>
	<description>A directory of resources about grammar in the field of technical communication.</description>
	<language>en-us</language>
	<atom:link href="http://tc.eserver.org/dir/Grammar.xml" rel="self" type="application/rss+xml" />
	<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>Grammar</title>
		<link>http://tc.eserver.org/dir/Grammar</link>
	</image>
	<item>
		<title>Semi-Definite Rules for the Indefinite Article</title>
		<link>http://tc.eserver.org/31183.html</link>
		<guid>http://tc.eserver.org/31183.html</guid>
		<description>Technical writing–perhaps more than any other sort of writing–gets read and used by people from every corner of the Anglophonic world. And people don’t get less sensitive to perceived slights or the appearance of cultural insensitivity because it’s a manual or help page. If anything, they’re more sensitive in such a circumstance.</description>
	</item>
	<item>
		<title>Rhetorical Grammar, 5th Edition</title>
		<link>http://tc.eserver.org/30690.html</link>
		<guid>http://tc.eserver.org/30690.html</guid>
		<description>Throughout the book, Kolln works to build the readers&apos; confidence and encourage them to think of grammar as a tool. Rhetorical Grammar is a textbook for undergraduate students, and Kolln keeps this target audience in mind by making the 322- page book user-friendly.</description>
	</item>
	<item>
		<title>Every Noun Can Be...</title>
		<link>http://tc.eserver.org/30358.html</link>
		<guid>http://tc.eserver.org/30358.html</guid>
		<description>When is a noun not a noun? When it&apos;s been verbed. A lot of verbing is going on, as you&apos;ve probably noticed. In fact, it&apos;s happening so frequently that I think we&apos;d better come up with a name for the part of speech produced by verbing a noun.</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 &quot;Correct&quot;</title>
		<link>http://tc.eserver.org/30338.html</link>
		<guid>http://tc.eserver.org/30338.html</guid>
		<description>I think it can be dangerous for a technical writer to be a grammar expert.</description>
	</item>
	<item>
		<title>To Err is Human, But Can It Be Forgiven?: Effects and Economics of Typos</title>
		<link>http://tc.eserver.org/30266.html</link>
		<guid>http://tc.eserver.org/30266.html</guid>
		<description>Technical communicators dread typos. A piece of work that contains one or more typos is seen as shoddy, not something to be proud of. Finding and correcting these errors, however, takes time and costs money. Might there be a better way to spend resources?- ways that might produce more usable information.? Effects of errors, value added by correcting them, and the economics of error detection will be discussed.</description>
	</item>
	<item>
		<title>Passive Voice Is Redeemed For Web Headings</title>
		<link>http://tc.eserver.org/30197.html</link>
		<guid>http://tc.eserver.org/30197.html</guid>
		<description>Active voice is best for most Web content, but using passive voice can let you front-load important keywords in headings, blurbs, and lead sentences. This enhances scannability and thus SEO effectiveness.</description>
	</item>
	<item>
		<title>Assembly Instructions for a Correct Sentence: The Sentence Diagram </title>
		<link>http://tc.eserver.org/30080.html</link>
		<guid>http://tc.eserver.org/30080.html</guid>
		<description>This workshop explores the whys and hows of sentence diagramming. Knowledge of the time-honored technique can aid editors, writers, and instructors in preventing and correcting pesky errors in sentence structure, including dangling modifiers, misplaced modifiers, and faulty parallelism. Diagramming offers the familiar look of technical drawings, the comforting feel of pencil on paper, and unmatched analytical potential.</description>
	</item>
	<item>
		<title>Emphasize This!</title>
		<link>http://tc.eserver.org/30051.html</link>
		<guid>http://tc.eserver.org/30051.html</guid>
		<description>Technical communicators tend to be problem solvers. We ask ourselves, &apos;How can I make this better?&apos; We don&apos;t want our instruction material to simply be serviceable; we want it to help make our readers&apos; lives easier. One way we do that is by anticipating mistakes that users might make if they don&apos;t read carefully. We use various techniques to emphasize material that could otherwise be overlooked. Some effective means of drawing the reader&apos;s eye to important material are presented below. Note that this article doesn&apos;t address safety messages. For proper use of safety messages, consult your corporate guidelines and the American National Standards Institute (ANSI).</description>
	</item>
	<item>
		<title>Some Thoughts on Teaching Grammar to Improve Writing</title>
		<link>http://tc.eserver.org/29886.html</link>
		<guid>http://tc.eserver.org/29886.html</guid>
		<description>The conviction that writing can be improved with a knowledge of grammar has prevailed for quite a long time. But research has shown no correlation between grammatical knowledge and writing ability.</description>
	</item>
	<item>
		<title>Double Take</title>
		<link>http://tc.eserver.org/29790.html</link>
		<guid>http://tc.eserver.org/29790.html</guid>
		<description>When I peer-review a four-page document and insert the word the seventeen times, I wonder: Is this what my company is paying me to do? Am I truly adding value for my customers?</description>
	</item>
	<item>
		<title>It&apos;s All Relative</title>
		<link>http://tc.eserver.org/29794.html</link>
		<guid>http://tc.eserver.org/29794.html</guid>
		<description>When it comes to relative pronouns, incomplete knowledge may lead to frustration and confusion. The pronouns that, which, who, and what serve as relative pronouns when they introduce a relative (or subordinate) clause.</description>
	</item>
	<item>
		<title>Sentence Diagramming: Making Sense of Sentences</title>
		<link>http://tc.eserver.org/29684.html</link>
		<guid>http://tc.eserver.org/29684.html</guid>
		<description>Sentence diagramming is an important tool for technical communicators to use in analyzing their own writing and editing. Sentence diagramming is also a neutral basis from which to discuss and evaluate technical documentation with colleagues and with other co- workers, such as subject-matter experts, who are not professional communicators. Through visual examples, this paper illustrates how to diagram three types of sentences (simple, compound, and complex), how sentence diagramming shows an objective view of three common syntactical errors (misplaced modifier, lack of parallel structure, and dangling modifier), and how the revised sentences make sense as sentences and as diagrams.</description>
	</item>
	<item>
		<title>Ten Grammar Mistakes That Make You Look Stupid</title>
		<link>http://tc.eserver.org/29382.html</link>
		<guid>http://tc.eserver.org/29382.html</guid>
		<description>These days, we tend to communicate via the keyboard as much as we do verbally. In general, we can slip up in a verbal conversation and get away with it. A colleague may be thinking, Did she just say &apos;irregardless&apos;?, but the words flow on, and our worst transgressions are carried away and, with luck, forgotten. That&apos;s not the case with written communications. When we commit a grammatical crime in e-mails, discussion posts, reports, memos, and other professional documents, there&apos;s no going back. Catching typos is easy (although not everyone does it). It&apos;s the other stuff -- correctly spelled but incorrectly wielded -- that sneaks through and makes us look stupid. Here&apos;s a quick review of some of the big ones.</description>
	</item>
	<item>
		<title>Equal Time: Grammar and Composition: Myths and Realities</title>
		<link>http://tc.eserver.org/29377.html</link>
		<guid>http://tc.eserver.org/29377.html</guid>
		<description>Let&apos;s resist seduction by the mythologies of teaching and keep our grasp on the realities of learning.</description>
	</item>
	<item>
		<title>America the Beautiful</title>
		<link>http://tc.eserver.org/29273.html</link>
		<guid>http://tc.eserver.org/29273.html</guid>
		<description>Writers of English have choices. Most every word we commit to paper (or its electronic equivalent) has a synonym</description>
	</item>
	<item>
		<title>The Indefinite &quot;We&quot; (Het &quot;Wij&quot;-Gevoel/Le &quot;Nous&quot; Indéfini)--Sender and Receiver References in Top-Down Communication: A Text Type-Based Approach</title>
		<link>http://tc.eserver.org/29089.html</link>
		<guid>http://tc.eserver.org/29089.html</guid>
		<description>In studies of political communication the use of personal pronouns is often put forward as one of the strategies for influencing sender-receiver relations (e.g., De Fina [1], Haverkate [2], Zupnik [3]). As Rogers and Swales [4] among others have demonstrated, similar techniques can be detected in corporate communication. In this article, the use of French and Dutch personal and possessive pronouns in the first person plural is examined in internal communication documents. The focus is on the link between text types and the use of inclusive, exclusive, or ambiguous we. First the research material is described; then a concise overview of the literary sources is given; finally the results of the research are discussed. It will be demonstrated that managers can exploit personal pronouns strategically and that the use of we is a parameter for identifying text function.</description>
	</item>
	<item>
		<title>A New Look at Infinitives in Business and Technical Writing</title>
		<link>http://tc.eserver.org/29074.html</link>
		<guid>http://tc.eserver.org/29074.html</guid>
		<description>This article begins by arguing that the infinitive phrase has not been taken seriously in writing because writers have been too concerned with Bishop Robert Lowth&apos;s proscription against the split infinitive. However, careful examination of three types of technical prose (instructions, annual reports, and &apos;junk mail&apos;) reveals that more than one sentence in four contains an infinitive phrase. The article then argues that two linguistic theories do not adequately explain the overwhelming presence of infinitives in the three types of prose. The reason for the presence of infinitives seems to be that they fulfill several rhetorical purposes, including vigor, symmetry, emphasis, variety, economy, and depersonalization. Implications for writing and teaching are also discussed.</description>
	</item>
	<item>
		<title>The Passive Voice and Social Values in Science</title>
		<link>http://tc.eserver.org/29077.html</link>
		<guid>http://tc.eserver.org/29077.html</guid>
		<description>This article claims that two social values in science--falsifiability of science and cooperation among scientists--determine use of passives in scientific communication. Scientists do not always develop valid theories, so scientific experiments must be amenable to being repeated and found invalid. This requires that the experiments must not be discrete events. Science is also a cooperative enterprise. As an integral part of science, scientific writing employs more passives than actives to focus on materials, methods, figures, processes, tables, concepts, etc. Use of passives to focus on the physical world helps de-emphasize discreteness of scientific experiments. Besides, it also helps remove personal qualifications of observing experimental results. Finally, it enhances cooperation among working scientists by providing a common knowledge base of scientific work--things and objects. Looked at in this way, the passive voice in scientific writing represents professional practices of science instead of personal stylistic choices of individual scientists.</description>
	</item>
	<item>
		<title>&quot;Unattached&quot; Clauses in Technical Writing</title>
		<link>http://tc.eserver.org/29011.html</link>
		<guid>http://tc.eserver.org/29011.html</guid>
		<description>The views concerning &quot;dangling participles&quot; of grammarians, usage experts and authors of books on technical writing are reviewed and compared. Although many unattached clauses are clearly unacceptable, some are less objectionable and still others are acceptable practice. Absolute constructions and other clause-relational participial, infinitival and verbless clauses need no attachment to a proximate noun or noun phrase, and logical clauses that are not attached to a noun are shown as normal, acceptable use. Even clearly adjectival clauses are often unattached when followed by the passive voice, intransitives and several other grammatical structures; clauses between the subject and verb and at the end of the sentence are also often not attached to the immediately preceding noun. Cultural (perhaps also gender) differences between humanistic teachers and task-oriented engineers are noted as possible causes of different viewpoints regarding the use of unattached participles, and greater acceptance of the many acceptable forms of unattached clauses is argued. &amp;lt;em&amp;gt;Suggested Reading Approach&amp;lt;/em&amp;gt; The first three sections (on principles, authoritative views and theoretical background) could be skimmed if you are already familiar with the background.</description>
	</item>
	<item>
		<title>It&apos;s All Relative</title>
		<link>http://tc.eserver.org/28635.html</link>
		<guid>http://tc.eserver.org/28635.html</guid>
		<description>When it comes to relative pronouns, incomplete knowledge may lead to frustration and confusion. The pronouns that, which, who, and what serve as relative pronouns when they introduce a relative (or subordinate) clause.</description>
	</item>
	<item>
		<title>Dangling for Position</title>
		<link>http://tc.eserver.org/28156.html</link>
		<guid>http://tc.eserver.org/28156.html</guid>
		<description>Dangling modifiers can be humorous for the reader, but humiliating for the writer. They&apos;re insidious, creeping into our prose and undermining our sentence structure. But they&apos;re easy to find if you know what to look for.</description>
	</item>
	<item>
		<title>Double Take</title>
		<link>http://tc.eserver.org/28157.html</link>
		<guid>http://tc.eserver.org/28157.html</guid>
		<description>If you write documentation for products that can be dangerous if misused, ambiguity is scarier than rush hour traffic on I-40. If you already know what the sentence means, it&apos;s difficult to perceive that it could be taken to mean something else. By stringently applying rules of grammar, you help eliminate potential ambiguity even when you don&apos;t perceive it. Technical content is difficult enough to navigate; give the reader a clear path so he can focus on the journey instead of the road.</description>
	</item>
	<item>
		<title>The Humble Hyphen</title>
		<link>http://tc.eserver.org/28161.html</link>
		<guid>http://tc.eserver.org/28161.html</guid>
		<description>The hyphen serves a single function. It joins things together: syllables of a word separated at the end of a line; two words used as a compound; or a modifier and the word it describes (when the combination itself is used as a modifier). But for the latter two functions, a hyphen isn&apos;t always needed. So how do you decide?</description>
	</item>
	<item>
		<title>Squiggles</title>
		<link>http://tc.eserver.org/28165.html</link>
		<guid>http://tc.eserver.org/28165.html</guid>
		<description>Thomas Mann described the writer as somebody for whom writing is more difficult than it is for other people. Nowhere is this truer than for comma use: while most folks float along blithely putting commas in or leaving them out at whim, we agonize over every squiggle. Why? Because we understand that the presence or absence of a comma can change the meaning of a sentence. In our line of work, unclear sentences can have dire consequences for our readers. So we worry.</description>
	</item>
	<item>
		<title>The Wicked Which and Other Fairytales</title>
		<link>http://tc.eserver.org/28167.html</link>
		<guid>http://tc.eserver.org/28167.html</guid>
		<description>Popular culture is filled with myths about grammar. Taught by generations of English teachers, these stories admonish little children to cling to the straight and narrow path, rather than venturing into the woods of creative communication. Some of these stories are usage guidelines rather than rules, but others are pure fantasy, the flight of some pedagogue&apos;s imagination.</description>
	</item>
	<item>
		<title>Write Right</title>
		<link>http://tc.eserver.org/28169.html</link>
		<guid>http://tc.eserver.org/28169.html</guid>
		<description>When you scan job postings for technical communicators, you&apos;ll find prospective employers seeking candidates who have an understanding of current technology, working knowledge of publishing tools, and time management skills. A bullet may ask for &apos;excellent writing and editing skills,&apos; but that bullet rarely appears at the top of the list. Not for me.</description>
	</item>
	<item>
		<title>The Blue Book of Grammar and Punctuation</title>
		<link>http://tc.eserver.org/28137.html</link>
		<guid>http://tc.eserver.org/28137.html</guid>
		<description>If you are still struggling to decode the complex jargon and structure of English grammar with a long list of reference books, relax. The long wait for a reader-friendly book on English grammar is over. With her straightforward and perfectly-logical approach, Jane Straus reveals the mysteries of grammar and punctuations in her book The Blue Book of Grammar and Punctuation. The book is extremely well-organized, allowing readers to quickly locate the required topics. Concepts are described in clear and simple phrases, backed with examples from everyday language usage.</description>
	</item>
	<item>
		<title>Writing Technical Specifications in the Present</title>
		<link>http://tc.eserver.org/27448.html</link>
		<guid>http://tc.eserver.org/27448.html</guid>
		<description>Technical specifications are improved in several ways with one easy procedure - writing them in the present tense. That is, rather than trying to specify constraints on a product that does not yet exist, describe the product as though it already existed.</description>
	</item>
	<item>
		<title>Fear Not the Long Sentence</title>
		<link>http://tc.eserver.org/27365.html</link>
		<guid>http://tc.eserver.org/27365.html</guid>
		<description>Everyone fears the long sentence. Editors fear it. Readers fear it. Most of all, writers fear it. Even I fear it. But...</description>
	</item>
	<item>
		<title>Control the Pace</title>
		<link>http://tc.eserver.org/27339.html</link>
		<guid>http://tc.eserver.org/27339.html</guid>
		<description>Control the pace of the story by varying sentence length.</description>
	</item>
	<item>
		<title>Period As a Stop Sign</title>
		<link>http://tc.eserver.org/27331.html</link>
		<guid>http://tc.eserver.org/27331.html</guid>
		<description>Place strong words at the beginning of sentences and paragraphs, and at the end. The period acts as a stop sign. Any word next to the period says, &apos;Look at me.&apos;</description>
	</item>
	<item>
		<title>Tech Writers, Grammar, and the Prescriptive Attitude</title>
		<link>http://tc.eserver.org/26615.html</link>
		<guid>http://tc.eserver.org/26615.html</guid>
		<description>Many tech writers do not see grammar as a set of conventions to help them write clearly. Instead, to judge by the wording of the questions and responses, they see grammar as a set of unchanging rules that can provide definitive answers in every situation.</description>
	</item>
	<item>
		<title>A Critique of Grammatical Coverage in Business-Communication Textbooks</title>
		<link>http://tc.eserver.org/26582.html</link>
		<guid>http://tc.eserver.org/26582.html</guid>
		<description>Business English (BE) and business communication (BC) overlap. English handles linguistic mechanics and style, whereas communication holistically discusses the movement of a message from one person to another.  The BC discipline, unfortunately, allows language basics into its pedagogy like a statistics course teaching fundamental mathematics.  From the other side, some English courses teach BC before their students are able to handle that material.  A subject teaches prepared students.  If they are deficient, they are either kept out or the subject matter suffers.</description>
	</item>
	<item>
		<title>The Not-So-Able able</title>
		<link>http://tc.eserver.org/26502.html</link>
		<guid>http://tc.eserver.org/26502.html</guid>
		<description>The suffix -able can be very useful in the English language because it helps us to express capability or worthiness. However, it&apos;s often bad form to pick any verb, slap -able on the end of it, and try to make a valid adjective.</description>
	</item>
	<item>
		<title>Punctuation, Punctuation, Punctuation</title>
		<link>http://tc.eserver.org/26276.html</link>
		<guid>http://tc.eserver.org/26276.html</guid>
		<description>A light touch with punctuation has always made sense, whether you&apos;re scratching out a sonnet on velum with a quill pen, or texting a mate on your mobile. It&apos;s meant to enhance communication, not hinder it.</description>
	</item>
	<item>
		<title>Punctuation by Languages</title>
		<link>http://tc.eserver.org/26173.html</link>
		<guid>http://tc.eserver.org/26173.html</guid>
		<description>Not too long ago, I was managing a translation project in Access (English to Greek) when I discovered that the translator hadn&apos;t used question marks similar to those used in the English source. Instead of question marks, he was using semicolons. I was sure that this was a mistake and that the computer was acting strange again. But it wasn&apos;t a mistake. In the Greek language, the question mark is like a semicolon, and the semicolon is instead a raised period. I&apos;ve started to check on other projects as well, and I&apos;ve learned quite a few interesting things about punctuation and their separators.</description>
	</item>
	<item>
		<title>Dodge the Grammar Traps</title>
		<link>http://tc.eserver.org/26151.html</link>
		<guid>http://tc.eserver.org/26151.html</guid>
		<description>You don&apos;t have to swallow a grammar book to write correctly. If you can just avoid ten serious and very common traps, your chances of making a grammar mistake drop dramatically.</description>
	</item>
	<item>
		<title>Sentence Types and Sentence Structures Revisited</title>
		<link>http://tc.eserver.org/26067.html</link>
		<guid>http://tc.eserver.org/26067.html</guid>
		<description>Before we discuss sentence types and structures, let us regard writing as a donut. When talking of sentence types, we will consider four building blocks of the donut.</description>
	</item>
	<item>
		<title>How to Write Good</title>
		<link>http://tc.eserver.org/26000.html</link>
		<guid>http://tc.eserver.org/26000.html</guid>
		<description>Fifty-two humorous rules about how to write well (each of which is broken).</description>
	</item>
	<item>
		<title>Fear of Punctuation</title>
		<link>http://tc.eserver.org/25796.html</link>
		<guid>http://tc.eserver.org/25796.html</guid>
		<description>So maybe you do know how to add memory to your computer or program your cell phone, but do you know where to put a comma in a sentence? If you have a sentence followed by a list, do you use a semicolon or a colon? Does the period go inside or outside of quotation marks? How do you keep up with changing rules of grammar and punctuation when you can&apos;t remember where to put the apostrophe? People often fear punctuation because the rules have changed and they continue to do so.</description>
	</item>
	<item>
		<title>GrammarNOW</title>
		<link>http://tc.eserver.org/25798.html</link>
		<guid>http://tc.eserver.org/25798.html</guid>
		<description>This site is dedicated to answering grammar, composition, or formatting questions.</description>
	</item>
	<item>
		<title>Gender-Free Legal Writing: Managing the Personal Pronouns</title>
		<link>http://tc.eserver.org/25005.html</link>
		<guid>http://tc.eserver.org/25005.html</guid>
		<description>Where a statement of any complexity is made about a person, the maker of the statement may face decisions about how further references should be framed.</description>
	</item>
	<item>
		<title>Collecting Books about Editing</title>
		<link>http://tc.eserver.org/24926.html</link>
		<guid>http://tc.eserver.org/24926.html</guid>
		<description>Intercom&apos;s &apos;friendly editor&apos; discusses his extensive collection of dictionaries, grammars, and other books of interest.</description>
	</item>
	<item>
		<title>Reconsidering Some Prescriptive Rules of Grammar and Composition</title>
		<link>http://tc.eserver.org/24162.html</link>
		<guid>http://tc.eserver.org/24162.html</guid>
		<description>Technical writers and editors are beset with rules. As authoritative as they are, published style guides such as The Chicago manual of style, MLA, APA, and Gregg do not address reading theory but hang their prescriptions on the flimsy mantle of tradition. This article challenges some putative rules of grammar and mechanics in an effort to improve technical texts for the people who read them.</description>
	</item>
	<item>
		<title>Style, Grammar, and Usage</title>
		<link>http://tc.eserver.org/23726.html</link>
		<guid>http://tc.eserver.org/23726.html</guid>
		<description>Information on style, grammar, and usage.</description>
	</item>
	<item>
		<title>The Use of Capitals</title>
		<link>http://tc.eserver.org/23407.html</link>
		<guid>http://tc.eserver.org/23407.html</guid>
		<description>The question to the list-subscribers was I am looking for studies dealing with the difference between small letters and capitals. Are small letters easier to read? In France, road signs are written in capitals but it is not the case in the US or Canada.</description>
	</item>
	<item>
		<title>Workshop: English Grammar</title>
		<link>http://tc.eserver.org/23168.html</link>
		<guid>http://tc.eserver.org/23168.html</guid>
		<description>A slideshow that presents some often-confused elements of English grammar.</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>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>Stressing What is Important in a Sentence</title>
		<link>http://tc.eserver.org/22131.html</link>
		<guid>http://tc.eserver.org/22131.html</guid>
		<description>In addition to expunging the usual collection of wordy phrases from documents, editors commonly attempt to tighten up writing to make it more direct, clear, and concise. For example, when editing business and technical material, I frequently change sentences containing &apos;it is,&apos; &apos;there is,&apos; and &apos;there are.&apos; Writers often ask me &apos;what was wrong with that sentence?&apos; I reply that although the sentence wasn&apos;t wrong grammatically, such phrases distract the reader from the important part of the message.</description>
	</item>
	<item>
		<title>Use of Hyphens</title>
		<link>http://tc.eserver.org/22134.html</link>
		<guid>http://tc.eserver.org/22134.html</guid>
		<description>This page collects a series of notes from readers of my newsletter, and my responses to those notes, arising from an article in &lt;A HREF=&quot;http://www.jeanweber.com/news/tenews60.htm&quot;&gt;issue 60, 13 May 2002&lt;/A&gt;. I thank those who took the time to write and explain &lt;i&gt;why&lt;/i&gt; some hyphen usage is considered to be correct or incorrect.</description>
	</item>
	<item>
		<title>Style Sheets and Grammar</title>
		<link>http://tc.eserver.org/21534.html</link>
		<guid>http://tc.eserver.org/21534.html</guid>
		<description>A collection of online resources about style guides and reference sites about grammar.</description>
	</item>
	<item>
		<title>Caught in the Active</title>
		<link>http://tc.eserver.org/20471.html</link>
		<guid>http://tc.eserver.org/20471.html</guid>
		<description>Have you been told, perhaps by your computerised grammar checker, that too many of your sentences are passive? Have you heard the rule of thumb that at least 80 percent of the sentences in any passage should be active? If you&apos;ve had the problem or heard the rule, and wonder what the terms active and passive mean, and why one is good and the other frowned on, this article is for you.</description>
	</item>
	<item>
		<title>Creative Indents</title>
		<link>http://tc.eserver.org/20433.html</link>
		<guid>http://tc.eserver.org/20433.html</guid>
		<description>Indenting the first line of every paragraph is a habit most of us acquired in grammar school. However, for those daring souls who have always insisted on coloring outside the lines, it’s time to consider using a different style paragraph indent. There are more options than you might have realized!</description>
	</item>
	<item>
		<title>Hyphens, En-Dashes and Em-Dashes</title>
		<link>http://tc.eserver.org/20420.html</link>
		<guid>http://tc.eserver.org/20420.html</guid>
		<description>Hyphens, en-dashes and em-dashes are frequently used punctuation marks that are just as frequently misunderstood. All three marks are essentially horizontal lines, though their lengths vary (as do, occasionally, their designs – see figure 1). However, these three different marks have very different purposes, and using a hyphen to do an m-dash’s job is just as much of a punctuation error as using a question mark in place of a comma.</description>
	</item>
	<item>
		<title>Participles Becoming Prepositions--Some Arcane Information for Editors</title>
		<link>http://tc.eserver.org/20151.html</link>
		<guid>http://tc.eserver.org/20151.html</guid>
		<description>A presentation that accompanies &lt;A HREF=&quot;http://tc.eserver.org/20150.html&quot;&gt;the paper of the same name&lt;/A&gt; at http://webhome.crk.umn.edu/~mpringle/UsingPaper.rtf.</description>
	</item>
	<item>
		<title>Participles Becoming Prepositions--Some Arcane Information for Editors</title>
		<link>http://tc.eserver.org/20150.html</link>
		<guid>http://tc.eserver.org/20150.html</guid>
		<description>In English, some participles have already become prepositions. The author noticed in her work as a technical editor that most of her writers seemed to perceive the participle &apos;using&apos; as a preposition already although it is not listed as such in the dictionary. The paper gives the evidence and rationale for making such a claim. It offers a window on written language change in progress and celebrates the language user’s ability to make the stolid dialect we call technical writing more vigorous and efficient by turning a participle into a preposition.</description>
	</item>
	<item>
		<title>Dr. Grammar</title>
		<link>http://tc.eserver.org/19165.html</link>
		<guid>http://tc.eserver.org/19165.html</guid>
		<description>Dr. Grammar may provide help with your grammar questions.</description>
	</item>
	<item>
		<title>Escape From the Grammar Trap</title>
		<link>http://tc.eserver.org/19180.html</link>
		<guid>http://tc.eserver.org/19180.html</guid>
		<description>Too many editors focus on the details and don&apos;t pay enough attention to the bigger picture. Editors can--and should--add even more value through substantive, technical, and usability editing.&#xD;&#xD;Copyediting is important, but the details are only part of what an editor can and should be reviewing. After all, a document can be correctly spelled and punctuated, grammatically correct, use only approved terminology, and follow the style guide perfectly--and still not serve the audience&apos;s needs.&#xD;&#xD;This article covers some reasons why editors focus on details and not the bigger picture; describes how much attention technical communicators should pay to formal rules of grammar, punctuation, and usage; and describes how we can distinguish between essential and nonessential rules of grammar, punctuation, and usage.</description>
	</item>
	<item>
		<title>The Passive in Technical and Scientific Writing</title>
		<link>http://tc.eserver.org/18980.html</link>
		<guid>http://tc.eserver.org/18980.html</guid>
		<description>Almost every discussion of technical or scientific style mentions the passive voice, usually as a stylistic evil to avoid. While I doubt that many of us would endorse such extreme prescriptions as &apos;Always use the active voice,&apos; or &apos;A writer will almost automatically improve his style when he shifts from passive to active constructions,&apos; we may be more ready to accept Freedman&apos;s position in &apos;The Seven Sins of Technical Writing.&apos; His Sin 6 is &apos;the Deadly Passive, or, better, deadening passive; it takes the life out of writing, making everything impersonal, eternal, remote and dead, but he adds that &apos;frequently, of course, the passive is not a sin and not deadly, for there simply is no active agent and the material must be put impersonally.&apos;</description>
	</item>
	<item>
		<title>Exercise Central</title>
		<link>http://tc.eserver.org/18854.html</link>
		<guid>http://tc.eserver.org/18854.html</guid>
		<description>Exercise Central is the largest collection of editing exercises available online that provide practice for mastering the skills of editing grammar, style, punctuation, and mechanics.</description>
	</item>
	<item>
		<title>Nominalizations and Their Impact on Readers</title>
		<link>http://tc.eserver.org/18217.html</link>
		<guid>http://tc.eserver.org/18217.html</guid>
		<description>The study presented here examined the effect of&#xD;nominalizations in technical documents on&#xD;readers’ recall and comprehension. Subjects read&#xD;one of two technical passages in either a&#xD;nominalized or denominalized form, and took&#xD;recall and comprehension tests. Results indicate&#xD;that denominalized passages can help readers&#xD;retain more information when the original&#xD;nominalizations are critical to the readers’&#xD;understanding of the passage.</description>
	</item>
	<item>
		<title>Teaching a Workshop on Sentence Diagramming</title>
		<link>http://tc.eserver.org/15202.html</link>
		<guid>http://tc.eserver.org/15202.html</guid>
		<description>Demonstrates how sentence diagramming can be an effective writing tool and offers tips on how it should be taught.</description>
	</item>
	<item>
		<title>Breaking the Rules</title>
		<link>http://tc.eserver.org/13554.html</link>
		<guid>http://tc.eserver.org/13554.html</guid>
		<description>In our early writing years, many of&#xD;us toiled under strict teachers who&#xD;drilled the rules of English grammar&#xD;into our collective consciousness.&#xD;We sweated drops of blood on our&#xD;pristine paper as we tried to craft perfect&#xD;sentences for that much-desired &apos;A.&apos; We&#xD;prayed that we didn’t leave a word or&#xD;clause misplaced or dangling for the&#xD;teacher’s angry red pen to mark.&#xD;Yet pick up a work of modern fiction,&#xD;and you might notice that the writer has&#xD;broken many of the rules that were&#xD;drummed into our impressionable heads.&#xD;These days, fiction often resembles the&#xD;casual style of postmodern poetry, with&#xD;sentence fragments and punctuation&#xD;sprinkled about like seasoning. But in&#xD;technical communication, we can’t be so&#xD;casual. We must adhere to those rules of&#xD;grammar our English teachers upheld—&#xD;at least, for the most part.</description>
	</item>
	<item>
		<title>The Good Grammar, Good Style™ Pages</title>
		<link>http://tc.eserver.org/13404.html</link>
		<guid>http://tc.eserver.org/13404.html</guid>
		<description>Do you have a question about style, grammar, or mechanics? Find the answer to your questions in the Good Grammar, Good Style Archive — over 100 pages of useful articles and frequently asked questions!</description>
	</item>
	<item>
		<title>Grammar, Spelling, and Punctuation</title>
		<link>http://tc.eserver.org/11851.html</link>
		<guid>http://tc.eserver.org/11851.html</guid>
		<description>A guide on punctuation, capitals, spelling, sentence construction and parts of speech.</description>
	</item>
	<item>
		<title>Conquering the Comma</title>
		<link>http://tc.eserver.org/10780.html</link>
		<guid>http://tc.eserver.org/10780.html</guid>
		<description>This presentation introduces your students to the rules of comma usage, including placement in compound sentences, after introductory elements, with dependent phrases and clauses, around non-essential elements, in a series, and with adjectives. This presentation also covers methods for avoiding a common comma error--the comma splice. This presentation is ideal for the beginning of a composition course, the assignment of a writing project, or as a refresher presentation for grammar usage.</description>
	</item>
	<item>
		<title>Commonly Used and Misused Punctuation Marks</title>
		<link>http://tc.eserver.org/10711.html</link>
		<guid>http://tc.eserver.org/10711.html</guid>
		<description>Defines the functions of several punctuation marks and provides examples of their correct usage.</description>
	</item>
	<item>
		<title>Grammar: A Handy Guide</title>
		<link>http://tc.eserver.org/10717.html</link>
		<guid>http://tc.eserver.org/10717.html</guid>
		<description>Normal rules of English grammar are often violated in technical writing, sometimes with good reason. However, writers are often not aware of these violations. This guide identifies some of the rules that are most commonly violated.</description>
	</item>
	<item>
		<title>The Online English Grammar</title>
		<link>http://tc.eserver.org/10672.html</link>
		<guid>http://tc.eserver.org/10672.html</guid>
		<description>Explains English parts of speech and gives several usage examples.</description>
	</item>
	<item>
		<title>The American Heritage Book of English Usage</title>
		<link>http://tc.eserver.org/10625.html</link>
		<guid>http://tc.eserver.org/10625.html</guid>
		<description>This book is designed to inform you about current problems in English usage so you can make intelligent decisions when communicating. When confronted with a choice about a usage, you may ask yourself a number of questions: Has this usage been criticized for some reason in the past? If so, are these criticisms substantial? What are the linguistic and social issues involved? Have people frequently applied this usage in the past, and for how long? What do well-respected writers think of the usage today? You will find answers to these and many other questions in this book.</description>
	</item>
	<item>
		<title>The Blue Book of Grammar and Punctuation</title>
		<link>http://tc.eserver.org/10640.html</link>
		<guid>http://tc.eserver.org/10640.html</guid>
		<description>Jane Straus&apos; easy-to-use reference guide and workbook is now available as an online resource. This popular book is an indispensable and entertaining guide for writers, proofreaders, editors, managers, clerical staff, teachers, and students. Use this site to find the answers to your questions concerning proper English grammar and punctuation. </description>
	</item>
	<item>
		<title>Common Errors in English</title>
		<link>http://tc.eserver.org/10644.html</link>
		<guid>http://tc.eserver.org/10644.html</guid>
		<description>Offers an extensive list of commonly confused words, their definitions and the correct way to use them.</description>
	</item>
	<item>
		<title>Grammar</title>
		<link>http://tc.eserver.org/10655.html</link>
		<guid>http://tc.eserver.org/10655.html</guid>
		<description>A website about English grammar for students.</description>
	</item>
	<item>
		<title>Guide to Grammar and Writing</title>
		<link>http://tc.eserver.org/10652.html</link>
		<guid>http://tc.eserver.org/10652.html</guid>
		<description>A web-based complete guide to English syntax and grammar.</description>
	</item>
</channel>
</rss>