<?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>Kestrel&#039;s Aerie &#187; grammar</title>
	<atom:link href="http://kestrelsaerie.com/tag/grammar/feed/" rel="self" type="application/rss+xml" />
	<link>http://kestrelsaerie.com</link>
	<description>An Eclectic Collection of Musings on Life, Living, and Blogging</description>
	<lastBuildDate>Thu, 02 Sep 2010 15:47:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Clearing Up the Confusion</title>
		<link>http://kestrelsaerie.com/2010/04/clearing-confusion/</link>
		<comments>http://kestrelsaerie.com/2010/04/clearing-confusion/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 21:23:35 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[confusables]]></category>
		<category><![CDATA[grammar]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2985</guid>
		<description><![CDATA[<h2>Confusables</h2>
<p>Recently, the fine folks at <a title="Home Page - copyediting.com" href="http://copyediting.com">copyediting.com</a> began a new <a title="Copyediting.com Podcasts: Confusables" href="http://www.copyediting.com/wordpress/?tag=confusables">series of podcasts</a> to address what they call &#8220;confusables&#8221;: those word pairs that give a lot of speakers and writers of English trouble because of their similarities in spelling or pronunciation. For example, they address discreet/discrete, disburse/disperse, loath/loathe, and inciteful/insightful. Some&#8230;</p><p><a href="http://kestrelsaerie.com/2010/04/clearing-confusion/">Clearing Up the Confusion</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<h2>Confusables</h2>
<p>Recently, the fine folks at <a title="Home Page - copyediting.com" href="http://copyediting.com">copyediting.com</a> began a new <a title="Copyediting.com Podcasts: Confusables" href="http://www.copyediting.com/wordpress/?tag=confusables">series of podcasts</a> to address what they call &#8220;confusables&#8221;: those word pairs that give a lot of speakers and writers of English trouble because of their similarities in spelling or pronunciation. For example, they address discreet/discrete, disburse/disperse, loath/loathe, and inciteful/insightful. Some confusables, I&#8217;ve discussed in the past; e.g., peak/peek/pique, their/there/they&#8217;re.</p>
<p>Often, what happens with many confusables is that the incorrect part of speech is used. This occurs when an adjective form is used instead of a noun or verb, or a noun is used instead of verb. For example, how many times have you seen the construction, &#8220;I need to cloth myself&#8221;? Clearly, the writer meant to use the verb &#8220;clothe,&#8221; not the noun &#8220;cloth.&#8221; As is the case with several confusables, the verb adds an <em>e</em> to the noun form (bath/bathe, for instance).</p>
<p>Other times, people simply don&#8217;t know which word they want to use. Such is often the case with discrete and discreet. The former means singular, or separate, such as &#8220;discrete pieces of information,&#8221; and the latter means prudent, showing good judgment, or unobtrusive: &#8220;&#8230;followed the subject at a discreet distance.&#8221;</p>
<h2>Affect – Effect</h2>
<p>One of the more prevalent confusions for a lot of people is when to use &#8220;affect&#8221; or &#8220;effect.&#8221; In fact, a friend asked me last week whether I&#8217;d discussed these words here. I hadn&#8217;t, but fortunately, she was able to find her answer at <a title="Grammar Girl: Quick and Dirty Tips" href="http://grammar.quickanddirtytips.com/">Grammar Girl</a>. To save you the trouble of searching, though, I&#8217;ll explain the difference here as well. In the simplest terms, &#8220;affect&#8221; is almost always a verb; &#8220;effect&#8221; is almost always a noun. And while both have adjectival forms – affective and effective – the adjective formed from the (usual) noun is almost always the one you see. One other thing to keep in mind: According to Web11, the noun form of <em>affect</em> stresses the first syllable; furthermore, the use of <em>affect</em> as a noun is so esoteric, I won&#8217;t even bother you with an example.</p>
<blockquote class="left"><p>&#8220;affect&#8221; is almost always a verb; &#8220;effect&#8221; is almost always a noun</p></blockquote>
<p>If you keep that in mind, you&#8217;ll (almost always) get it right. Let&#8217;s look at some examples:</p>
<blockquote><p>Her perfume always had a significant effect on him: His eyes watered, and he&#8217;d sneeze every five or ten minutes. (effect, noun)</p>
<p>Her perfume affected him all the time, but generally not the way she intended. (affect, verb)</p>
<p>John was desperate to effect a solution that would satisfy all parties.</p>
<p>Unfortunately, John&#8217;s solution wasn&#8217;t very effective.</p></blockquote>
<h2>Flaunt – Flout</h2>
<p>Granted, these two words aren&#8217;t used quite as much as &#8220;affect&#8221; and &#8220;effect,&#8221; but that may contribute even more to their confusion.</p>
<p>&#8220;Flaunt&#8221; means to display ostentatiously or impudently, or to treat with contempt:</p>
<blockquote><p>Back in the &#8217;70s, Morganna flaunted her bosom at baseball games and other sporting events.</p>
<p>Al Capone flaunted his ill-gotten riches until he was convicted of tax evasion.</p></blockquote>
<p>&#8220;Flout&#8221; is similar to the second sense of &#8220;flaunt,&#8221; that is, to treat with contemptuous disregard. But <em>Webster&#8217;s Concise Dictionary of English Usage </em>cautions against using &#8220;flaunt&#8221; when you really mean &#8220;flout&#8221;:</p>
<blockquote><p>Capone flouted Prohibition until Eliot Ness&#8217;s &#8220;Untouchables&#8221; nailed him for income tax evasion.</p></blockquote>
<h2>Pitfall – Pratfall</h2>
<p>Personally, I don&#8217;t understand the confusion here, but I&#8217;ve seen both words misused recently, so apparently some people don&#8217;t grasp the difference. A &#8220;pitfall&#8221; (besides being an old Atari console game title) is a trap or snare, often one that is crudely covered, or a hidden or not easily recognized danger. A &#8220;pratfall&#8221; is something you see in vaudeville comedy: a fall on the buttocks, or a humiliating mishap or blunder.</p>
<blockquote><p>One of the pitfalls of putting oneself as an expert in a field, is the occasional pratfall that happens when you err egregiously, whether by accident or not.</p></blockquote>
<h2>Wrap-Up</h2>
<p>I hope this short introduction to the pitfalls of confusables will have the desired effect of affecting your writing in a positive manner. After all, we don&#8217;t want to flaunt our ignorance, do we?</p>
<p>Any other confusables you&#8217;d like to discuss? Let us know in the comments!</p>
<p><a href="http://kestrelsaerie.com/2010/04/clearing-confusion/">Clearing Up the Confusion</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/04/clearing-confusion/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>National Grammar Day: A Quiz</title>
		<link>http://kestrelsaerie.com/2010/03/national-grammar-day-quiz/</link>
		<comments>http://kestrelsaerie.com/2010/03/national-grammar-day-quiz/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 12:10:29 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[National Grammar Day]]></category>
		<category><![CDATA[punctuation]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2829</guid>
		<description><![CDATA[<p>Believe it or not, today&#8211;March 4&#8211;is <a href="http://nationalgrammarday.com/">National Grammar Day</a>. To help celebrate this auspicious occasion, and to further grammar education throughout the Internet (always capitalized, incidentally), I have combed through hundreds&#8211;maybe even thousands&#8211;of blog entries to bring you the following quiz.</p>
<p><img class="size-full wp-image-2842 alignleft" style="margin-top: 5px; margin-bottom: 5px; margin-left: 15px; margin-right: 15px;" title="grammar-day-badge" src="http://kestrelsaerie.us/wp-content/uploads/2010/03/grammar-day-badge.png" alt="I support National Grammar Day" width="125" height="125" /></p>
<p>What you are about to see are errors of usage I have collected over the past few weeks,&#8230;</p><p><a href="http://kestrelsaerie.com/2010/03/national-grammar-day-quiz/">National Grammar Day: A Quiz</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Believe it or not, today&#8211;March 4&#8211;is <a href="http://nationalgrammarday.com/">National Grammar Day</a>. To help celebrate this auspicious occasion, and to further grammar education throughout the Internet (always capitalized, incidentally), I have combed through hundreds&#8211;maybe even thousands&#8211;of blog entries to bring you the following quiz.</p>
<p><img class="size-full wp-image-2842 alignleft" style="margin-top: 5px; margin-bottom: 5px; margin-left: 15px; margin-right: 15px;" title="grammar-day-badge" src="http://kestrelsaerie.us/wp-content/uploads/2010/03/grammar-day-badge.png" alt="I support National Grammar Day" width="125" height="125" /></p>
<p>What you are about to see are errors of usage I have collected over the past few weeks, saving them up especially for today. The authors shall remain anonymous, and if you happen to recognize your own writing herein, I trust you’ll appreciate that I mean no disrespect, and I sincerely hope you don’t take these examples as a personal affront: I assure you, no such motive exists. All I want to do is illuminate “real-life” examples of “what not to do.”</p>
<p>Some of these are minor, some more serious. All of them detract from the flow of the writer’s ideas, and at least for me, negatively affect my reading experience. Without further ado (not “adieu,” for heaven’s sake!), here are 10 items to test your grammar savvy. The answers are in the footnotes, but try not to read them before figuring out the problems for yourself.</p>
<ol>
<li>Do you think it is going to become the new paradigm that Google is pushing it as, or is it going to be the next amazing technology no one uses (ie: Segway)?<sup class='footnote'><a href='#fn-2829-1' id='fnref-2829-1'>1</a></sup></li>
<li>When I was looking all this up, I was stunned to see that Super Bowl XI (Raiders-Vikings in the Rose Bowl) was played Jan. 9, 1977. Just for comparison sake, this postseason, the first day of the first-round games were played on Jan. 9. (Ed.: The first sentence is for context only.)<sup class='footnote'><a href='#fn-2829-2' id='fnref-2829-2'>2</a></sup></li>
<li>On Friday night, the Saints&#8217; staff at the combine gathered in a private room at St. Elmo Steakhouse, an 108-year-old Indy landmark&#8230;.<sup class='footnote'><a href='#fn-2829-3' id='fnref-2829-3'>3</a></sup></li>
<li>In 2010, National Grammar Day is hosted by Mignon Fogarty the author of the New York Times best-selling book <a href="http://us.macmillan.com/grammargirlsquickanddirtytipsforbetterwriting">Grammar Girl&#8217;s Quick and Dirty Tips for Better Writing</a> and <a href="http://us.macmillan.com/thegrammardevotional">The Grammar Devotional</a>.<sup class='footnote'><a href='#fn-2829-4' id='fnref-2829-4'>4</a></sup></li>
<li>Something that solo’s well, can still do dungeons, and can run battlegrounds as well. (Disregard that this is a sentence fragment: It’s a stylistic convention, and works in context.)<sup class='footnote'><a href='#fn-2829-5' id='fnref-2829-5'>5</a></sup></li>
<li>If it’s a problem with myself, a situation, conflicts, or policy issues, that it be brought up with myself or an officer first to see if it can be resolved.<sup class='footnote'><a href='#fn-2829-6' id='fnref-2829-6'>6</a></sup></li>
<li>Keep current clients at their usual rate, and only quote your new rate to potential customers that want to work with you.<sup class='footnote'><a href='#fn-2829-7' id='fnref-2829-7'>7</a></sup></li>
<li>And wtf…we are a community are we not?!<sup class='footnote'><a href='#fn-2829-8' id='fnref-2829-8'>8</a></sup></li>
<li>WOW’s default UI is not optimal, but we can get around this due to it’s extensibility.<sup class='footnote'><a href='#fn-2829-9' id='fnref-2829-9'>9</a></sup></li>
<li>First we see that the ability is now a raid wide Aura.  Instead of a Self Buff that occurs only when your pet scores a critical hit.<sup class='footnote'><a href='#fn-2829-10' id='fnref-2829-10'>10</a></sup></li>
</ol>
<p>Thanks for playing! So how&#8217;d you do? Again, I want to emphasize my intent here is not to belittle or poke fun at any of the writers. Rather, I simply want to help you (and them) write better. Now, go out and write right!
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2829-1'> In this sentence, <em>ie</em> should be <em>i.e.</em> Even better, replace it with <em>e.g.</em> (for example). Also, replace the colon with a comma. <span class='footnotereverse'><a href='#fnref-2829-1' >&#8617;</a></span></li>
<li id='fn-2829-2'> “Just for ______ sake” should be possessive; thus, “Just for comparison’s sake&#8230;.” Better: “Just for the sake of comparison&#8230;.” Also, the last part of the sentence should read, “&#8230;the first day of the first-round games was Jan. 9&#8230;” <em>or</em> “&#8230;the first-round games were played on (or started on) Jan. 9&#8230;.” Finally, if I were writing, I&#8217;d have said, &#8220;When I was looking up all this&#8230;&#8221; but I&#8217;m not going to get hypercritical. <span class='footnotereverse'><a href='#fnref-2829-2' >&#8617;</a></span></li>
<li id='fn-2829-3'> &#8230;St. Elmo Steakhouse, a 108-year-old&#8230;. (I told you some of these would be easy!) Incidentally, the plural possessive <em>Saints&#8217;</em> is correct. <span class='footnotereverse'><a href='#fnref-2829-3' >&#8617;</a></span></li>
<li id='fn-2829-4'> I almost hated to do this, but it’s rather amusing. This comes from the “About the Host” blurb at the National Grammar Day site (linked in the opening paragraph). There should be a comma after Fogarty, and it should be “best-selling <em>books</em>” (plural). <span class='footnotereverse'><a href='#fnref-2829-4' >&#8617;</a></span></li>
<li id='fn-2829-5'> There is no such thing as a possessive verb: lose the apostrophe in “solos.” <span class='footnotereverse'><a href='#fnref-2829-5' >&#8617;</a></span></li>
<li id='fn-2829-6'> <em>Myself</em> and similar pronouns are used either intensively (I did the job <em>myself</em>) or reflexively (I hurt <em>myself</em>). In other words, they need a referent; in this case, the pronoun <em>I.</em> Thus, you can&#8217;t use <em>myself</em> in the example here, since there is no referent for <em>myself: </em>Instead, the pronoun should be <em>me</em> (in both instances!). Also, there is something missing before &#8220;&#8230;that it be brought up,&#8221; probably something along the lines of &#8220;I ask&#8221;. That&#8217;s more a proofreading issue than a true grammar problem. <span class='footnotereverse'><a href='#fnref-2829-6' >&#8617;</a></span></li>
<li id='fn-2829-7'> This one is a bit tricky, but it&#8217;s an error I see all too frequently. Customers are <em>people, </em>not things; thus, &#8220;&#8230;customers <em>who</em> want to work with you.&#8221; <span class='footnotereverse'><a href='#fnref-2829-7' >&#8617;</a></span></li>
<li id='fn-2829-8'> This one&#8217;s mostly for fun; however, there should be a comma after <em>community</em>. And really, the <a title="All about the interrobang." href="http://interrobang-mks.com/" target="_self">interrobang</a> is <em>not </em>a recognized punctuation mark; if you&#8217;re asking a question, stick with the question mark. If you want to add emphasis to the question (generally not desirable), <em>use italics.</em> But please, don&#8217;t conjoin exclamation points and question marks, okay!? <span class='footnotereverse'><a href='#fnref-2829-8' >&#8617;</a></span></li>
<li id='fn-2829-9'> Consider this a freebie: Once again, <em>it&#8217;s</em> is only, and always, a contraction for <em>it is. </em>The possessive <em>its, </em>like any possessive pronoun, never has an apostrophe. If you didn&#8217;t catch this one, click the <a title="Kestrel on Grammar" href="http://kestrelsaerie.us/category/writing/grammar/" target="_self">Grammar category</a> here and start from the beginning. *grin* <span class='footnotereverse'><a href='#fnref-2829-9' >&#8617;</a></span></li>
<li id='fn-2829-10'> Granted, WoW blogs use a lot of jargon that you may not see in &#8220;mainstream&#8221; blogs; still, even WoW bloggers should know and observe the rules. You might want to put a comma after <em>First</em> in the first sentence, and I won&#8217;t argue. But I won&#8217;t chastise the writer for the omission, either. But let&#8217;s look at the modifier(s) of &#8220;Aura&#8221; (which I wouldn&#8217;t capitalize, but I&#8217;ll buy an argument based on style—and jargon. So are we talking &#8220;raid Aura&#8221;? Possibly. What about a &#8220;wide Aura&#8221;? Perhaps. Much more likely, however, is a &#8220;raid-wide Aura.&#8221; Wouldn&#8217;t you agree? The &#8220;sentence&#8221; beginning with &#8220;Instead of&#8230;&#8221; is really a sentence fragment. So what I&#8217;d much prefer to see here is, &#8220;&#8230;a raid-wide aura, instead of a self-buff&#8230;.&#8221; (Yeah, I snuck in an extra hyphen; so did you, right?) <span class='footnotereverse'><a href='#fnref-2829-10' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/03/national-grammar-day-quiz/">National Grammar Day: A Quiz</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/03/national-grammar-day-quiz/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Two-Minute Drill: The Comma Splice</title>
		<link>http://kestrelsaerie.com/2010/02/comma_splice/</link>
		<comments>http://kestrelsaerie.com/2010/02/comma_splice/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 20:55:14 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[comma splice]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[punctuation]]></category>
		<category><![CDATA[two-minute drill]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2758</guid>
		<description><![CDATA[<p>For some reason, discussion of comma splices is on the upswing lately. I&#8217;ve run across it at least three times in recent weeks; most recently, at Copyediting&#8217;s <a title="Copyediting: Fiddly Rules Podcast #12 - The Comma Splice" href="http://www.copyediting.com/wordpress/?p=308&#38;prod_abbv=ce">Fiddly Rules Podcast #12</a>.<sup class='footnote'><a href='#fn-2758-1' id='fnref-2758-1'>1</a></sup> Because it&#8217;s unlikely you visit the same websites (or subscribe to the same blogs) as I do, I thought&#8230;</p><p><a href="http://kestrelsaerie.com/2010/02/comma_splice/">Two-Minute Drill: The Comma Splice</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p>For some reason, discussion of comma splices is on the upswing lately. I&#8217;ve run across it at least three times in recent weeks; most recently, at Copyediting&#8217;s <a title="Copyediting: Fiddly Rules Podcast #12 - The Comma Splice" href="http://www.copyediting.com/wordpress/?p=308&amp;prod_abbv=ce">Fiddly Rules Podcast #12</a>.<sup class='footnote'><a href='#fn-2758-1' id='fnref-2758-1'>1</a></sup> Because it&#8217;s unlikely you visit the same websites (or subscribe to the same blogs) as I do, I thought I&#8217;d give a quick lesson on this sometimes troublesome bugaboo.<sup class='footnote'><a href='#fn-2758-2' id='fnref-2758-2'>2</a></sup></p>
<p>First of all, what <em>is</em>&nbsp;a &quot;comma splice&quot;? Very simply, it&#8217;s the joining of two independent clauses with a comma, but without a coordinating conjunction. Here are a few examples:</p>
<ul>
<li>We bought a lot of chocolate chips on sale, my wife is baking cookies today.</li>
<li>I&#8217;m hungry, I don&#8217;t want to fix anything too complicated.</li>
<li>I looked at my weekly word count earlier, I was a couple hundred words below my goal.</li>
</ul>
<p>Many of you may see those as examples of &quot;run-on sentences,&quot; which they are. There are a lot of other ways to create run-ons; a comma splice is one of the simplest.&nbsp;</p>
<p>Earlier, I mentioned &quot;coordinating conjunctions.&quot; Coordinating conjunctions are <em>and, but, or, for, nor, yet, so</em>. &nbsp;Each of the examples I gave can be fixed by inserting a conjunction:</p>
<ul>
<li>We bought a lot of chocolate chips on sale, <em>so</em> my wife is baking cookies today.</li>
<li>I&#8217;m hungry, <em>but</em>&nbsp;I don&#8217;t want to fix anything too complicated.</li>
<li>I looked at my weekly word count earlier, <em>and&nbsp;</em>I was a couple hundred words below my goal.</li>
</ul>
<p>Note that the comma is still required before the conjunction, because the clauses are independent, or unrelated.</p>
<p>I&#8217;m sure many of you figured out different ways to eliminate the comma splice besides using conjunctions. For example, instead of trying to join the two independent clauses, you can simply make two sentences: &quot;I looked at my weekly word count earlier. I was a couple hundred words below my goal.&quot; This is probably the easiest &quot;fix,&quot; but it doesn&#8217;t always have the desired effect.</p>
<p>Likewise, many of you probably came up with another alternative: the semicolon. Use a semicolon if the two independent clauses are related to each other, and you want to add variety to your sentence structure:</p>
<ul>
<li>I&#8217;m hungry; I think I&#8217;ll fix some lunch.</li>
<li>I looked at my weekly word count earlier; I was a couple hundred words below my goal.</li>
</ul>
<p>In short, then, there are three ways to correct a comma splice:</p>
<ul>
<li>Use a coordinating conjunction after the comma.</li>
<li>Use a period instead of a comma.</li>
<li>Use a semicolon instead of a comma.</li>
</ul>
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2758-1'> Except when I went to listen to the podcast, the link took me to Fiddly Rule #11; hopefully, it&#8217;ll be fixed soon! <span class='footnotereverse'><a href='#fnref-2758-1' >&#8617;</a></span></li>
<li id='fn-2758-2'> Other Resources: <a title="" href="http://grammar.quickanddirtytips.com/comma-splice.aspx">Grammar Girl –&nbsp;Comma Splice</a>; <a title="" href="http://grammar.quickanddirtytips.com/semicolons.aspx">Grammar Girl&nbsp;– Semicolons</a>. <span class='footnotereverse'><a href='#fnref-2758-2' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/02/comma_splice/">Two-Minute Drill: The Comma Splice</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/02/comma_splice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Pro and Con View of Language</title>
		<link>http://kestrelsaerie.com/2010/02/pro-con-view-language/</link>
		<comments>http://kestrelsaerie.com/2010/02/pro-con-view-language/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 15:27:02 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[language]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/2010/02/a-pro-and-con-view-of-language/</guid>
		<description><![CDATA[<p>I was talking with a friend on Saturday, and our discussion caused my thoughts to spin off on a totally unrelated tangent (although I eventually brought it back to a point we were discussing). I asked,&#160; “Do you know why I love words so much?”</p>
<p>And suddenly that started me off on a dissertation I had no intention of delivering.&#8230;</p><p><a href="http://kestrelsaerie.com/2010/02/pro-con-view-language/">A Pro and Con View of Language</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p>I was talking with a friend on Saturday, and our discussion caused my thoughts to spin off on a totally unrelated tangent (although I eventually brought it back to a point we were discussing). I asked,&nbsp; “Do you know why I love words so much?”</p>
<p>And suddenly that started me off on a dissertation I had no intention of delivering. But, as egotistical as I am, I thought it sounded good (and my friend either had the courtesy, or as I prefer to think of it, the perspicacity, to not disabuse me of the idea that I might be on to something), so I’m going to present my thesis for your consideration.</p>
<p>Words fascinate me because they are so weak, so ineffective in truly communicating with one another.<sup class='footnote'><a href='#fn-2749-1' id='fnref-2749-1'>1</a></sup> People perceive them to be so powerful (“the pen is mightier than the sword”) only because we are reluctant, or afraid, to use our older, more basic, more effective forms of communication.</p>
<p>In prehistory, humans<sup class='footnote'><a href='#fn-2749-2' id='fnref-2749-2'>2</a></sup> learned to communicate effectively long before we learned to speak, and much earlier than we learned to write. Early man used gestures, pantomime, demonstration, and perhaps art (drawing) to transmit ideas. Looking at where evolution has taken us, it’s evident our early efforts at communicating were effective.&nbsp;</p>
<p>In fact, in some quarters, we’ve “reverted” to using gestures: Consider a SWAT team or a military sapper team. The leader points to a couple team members, indicates a direction for them to go. He repeats that with successive pairs, then gives a nonverbal signal to act. Similarly, our ancestors hunted game (think mammoths) in a similar manner.</p>
<blockquote class="right"><p>Language allows us to communicate more efficiently, <i>not</i> more effectively.</p></blockquote>
<p>Language has enabled us to communicate more <i>efficiently</i>, not more effectively. I’m not saying words are unnecessary; anymore, they are hugely necessary. But we have evolved to using them as a crutch.&nbsp;</p>
<p>Most of us have been to a funeral, or a wedding. What do people do at funerals (or weddings, for that matter)? How do they comfort the bereaved, or congratulate the newlyweds, and their parents? Many people offer verbal platitudes and words of comfort, but I think we all recognize they are words of convention.</p>
<p>The real communication is nonverbal: People touch, in one way or another. They shake hands; they kiss; they hug. They communicate with a smile, a laugh, a look; some cry. </p>
<p>In those looks, those touches, those hugs, they are saying, &quot;I care. I, too, am bereft. I feel your hurt.&quot; Or at a wedding, “I am glad for you. I am happy that you are happy. I am happy for your children, your friends, or whoever else’s joy we are celebrating.”</p>
<p>In it&#8217;s simplest, most basic form, they are saying, &quot;I care about you. I care for you.&quot;</p>
<p>But outside such emotionally charged circumstances (there are others; I’m sure you can think of some), we generally use words, spoken or written, to communicate.</p>
<p>Of course, there&#8217;s a valid argument to be made that words—language—developed to fill a void in how we communicate with our other senses, but I submit that void has widened considerably since we learned to speak and write.</p>
<blockquote class="left"><p>Language facilitated our ability to lie</p></blockquote>
<p>For one thing, language facilitated our ability to lie to each other. There is a drama currently on television, called “Lie To Me.” The premise, founded on real science, is that by studying a person’s voice and physical clues when they are talking, a trained observer can determine, unequivocally, whether someone is telling the truth or hiding the truth. </p>
<p>As language evolved, we humans, being a relatively lazy bunch, devolved to the point where others do not as readily perceive the subtle changes in our demeanor when we lie. Thus, it has become increasingly simple for us to deceive each other.</p>
<p>Animals, on the other hand, don’t have language: Watch a couple strange dogs approach each other. They communicate totally through nonverbal behaviors. Yet there is no question, after a short time, which one has established dominance, whether they are friendly, or whether one feels threatened by the other.</p>
<p>To some extent, we do the same, but we don’t all apply the same conventions or interpretations. For example, when I meet someone new, I shake hands with that person. My grip is firm, but not bone-crushing; I am usually looking for the same in return. Someone with a weak grip is either unused to shaking hands or lacks self-confidence, in my judgment. Someone with a bone-crushing grip is trying to show off his strength (I’m unimpressed, generally—and my arthritis certainly doesn’t appreciate it) or is trying to be the alpha-dog. I don’t automatically buy into that, either: My ego is too big to be easily subordinated by a handshake, no matter how strong. In fact, I usually wonder what the other person is trying to compensate for with that sort of grip. </p>
<p>So just in this common behavior, we can see a wide range of interpretations. I’m not claiming my interpretations are correct; in fact, it’s no doubt a fallacy for me to project my interpretations of a handshake on others, when in fact, there may be no intent whatsoever.</p>
<p>But, don’t we do the same thing with language? Don’t you arrive at some conclusions about me, based on the words I use? For instance, I used the word “premise” a couple paragraphs earlier, when I could just as easily used “basic idea” or, more simply, “idea.” You probably didn’t think much about that, but what about when I used “subordinated” a couple paragraphs up? Did the word give you pause? If so, why? Even as early as the second paragraph, I used “perspicacity” and “disabuse.” </p>
<p>I started this article with a question: “Why do I love words?” It’s time for me to answer more directly than I have so far. By way of analogy, let’s look at the value of pi: Most of us know it as 3.14, and for the vast majority of us, that works (or did, when we were doing geometry in school). And for the vast majority of us, a well-rounded vocabulary serves us very well. But occasionally, we need to be more precise in our language, just as an astronomer or astrophysicist needs to be much more exact with the value of pi. So, I love words because they allow us to be more precise, more accurate, in how we communicate.</p>
<p>This is where we come full circle: While I argue words are less effective in communication than physical behaviors (I know, I know: what’s the gesture for “perspicacity”?), by choosing words precisely, we can be more efficient in what we’re trying to communicate. Hopefully, if you’re unfamiliar with “perspicacity,” the context in which I used it helped you to understand that my friend acutely discerned I might be on to something.</p>
<p>Am I, though? I’m very interested in your opinions on this idea that language has lessened the effectiveness of our ability to communicate nonverbally. Let’s discuss in the comments.</p>
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2749-1'> At least in English, and since that is really the only language I know well, that’s the one from which I’m going to draw all my broad generalizations. <span class='footnotereverse'><a href='#fnref-2749-1' >&#8617;</a></span></li>
<li id='fn-2749-2'> I use the term loosely to encompass more than just <em>homo sapiens</em>. <span class='footnotereverse'><a href='#fnref-2749-2' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/02/pro-con-view-language/">A Pro and Con View of Language</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/02/pro-con-view-language/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Weekly Word Count: January 22</title>
		<link>http://kestrelsaerie.com/2010/01/weekly-word-count-january-22/</link>
		<comments>http://kestrelsaerie.com/2010/01/weekly-word-count-january-22/#comments</comments>
		<pubDate>Fri, 22 Jan 2010 16:44:40 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Personal]]></category>
		<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[accountability]]></category>
		<category><![CDATA[Copyediting]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[punctuation]]></category>
		<category><![CDATA[weekly word count]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2718</guid>
		<description><![CDATA[<p><span style="color: #111111; font-family: Corbel,'Lucida Grande','Lucida Sans Unicode',Arial,sans-serif; font-size: 14px; line-height: 22px;"><br />
</span></p>
<h2 style="margin: 1.833em 0px 0.611em; padding: 0px; font-weight: bold; color: #226699 ! important; font-size: 1.5em; line-height: 1.222em;">What Is This?</h2>
<p style="margin: 0px 1.571em; padding: 0px;">Following the lead of my mentor, friend, and exemplar, <a style="margin: 0px; padding: 0px; text-decoration: none; color: #226699; font-weight: bold;" title="Tami Moore's blog" href="http://tamimoore.com">Tami Moore</a>, this is a weekly article to document progress in meeting&#8230;</p><p><a href="http://kestrelsaerie.com/2010/01/weekly-word-count-january-22/">Weekly Word Count: January 22</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p><span style="color: #111111; font-family: Corbel,'Lucida Grande','Lucida Sans Unicode',Arial,sans-serif; font-size: 14px; line-height: 22px;"><br />
</span></p>
<h2 style="margin: 1.833em 0px 0.611em; padding: 0px; font-weight: bold; color: #226699 ! important; font-size: 1.5em; line-height: 1.222em;">What Is This?</h2>
<p style="margin: 0px 1.571em; padding: 0px;">Following the lead of my mentor, friend, and exemplar, <a style="margin: 0px; padding: 0px; text-decoration: none; color: #226699; font-weight: bold;" title="Tami Moore's blog" href="http://tamimoore.com">Tami Moore</a>, this is a weekly article to document progress in meeting my writing goals <a style="margin: 0px; padding: 0px; text-decoration: none; color: #226699; font-weight: bold;" title="Kestrel's Aerie: Goals for 2010" href="http://kestrelsaerie.us/2010/01/goals-2010/">as described here</a>.</p>
<p style="margin: 0px 1.571em; padding: 0px;">
<p style="margin: 0px 1.571em; padding: 0px;">I set up an Excel spreadsheet to track all my work by category (blog post, copyediting work, creative writing) and item. So all I need to do is add up the “words” column and I’m good to go. I&#8217;ve also decided to give this article half-credit, since I do a bit more than just paste boilerplate and fill in numbers (see the next section, for example). However, it will be counted in the following week&#8217;s total.</p>
<h2 style="margin: 1.833em 0px 0.611em; padding: 0px; font-weight: bold; color: #226699 ! important; font-size: 1.5em; line-height: 1.222em;">How Did I Do?</h2>
<p style="margin: 0px 1.571em; padding: 0px;">My weekly goal is <strong>1,500</strong> words.This week, I published two articles to the blog. I also did the first run-through on copyediting Tami&#8217;s <em>Choose: Volume 1 &#8211; The Search for a Captain. </em>For accountability purposes, I&#8217;m counting copyediting at ten percent of the original word count. I also prepared a style sheet for <em>Choose, </em>which I am counting at 25 percent.<sup class='footnote'><a href='#fn-2718-1' id='fnref-2718-1'>1</a></sup></p>
<p style="margin: 0px 1.571em; padding: 0px;">
<p style="margin: 0px 1.571em; padding: 0px;"><em> </em>I should say, right off the bat, rereading the first several episodes of <em><a title="Choose: An Interactive Web Serial" href="http://tamimoore.com/choose/">Choose</a> </em>was loads of fun. I found things I&#8217;d completely forgotten about, and laughed out loud at several passages (no, not because they were bad, but because they were hilariously funny!). I can&#8217;t wait for Tami to finish this project and publish it, so we—you and I—can all read it again, in one sitting.</p>
<p style="margin: 0px 1.571em; padding: 0px;">
<p style="margin: 0px 1.571em; padding: 0px;">This first major copyediting project has been a real eye-opener. I&#8217;ve edited several chapters of <em><a title="Feather Path - serial novel" href="http://www.irisharper.com/home/category/feather-path">Feather Path</a> </em>for <a title="Iris Harper's writing blog" href="http://irisharper.com">Iris Harper</a>, as well as <a title="TMI: How much is too much?" href="http://tmi.gunlovingdwarfchick.com/">Bre&#8217;s</a> short story, <em>Waking Iris, </em>but <em>Choose </em>is at least as large as the preceding, combined. And because I&#8217;m looking at the entirety of the document at one time, rather than just a few pages, I&#8217;m approaching this from a completely different perspective. It really makes me want to go back to those earlier manuscripts, and give them the same attention I&#8217;m devoting to <em>Choose. </em>However, I have projects for both ladies pending, and I promise to give them the same, more in-depth treatment that Tami&#8217;s manuscript is receiving.</p>
<p style="margin: 0px 1.571em; padding: 0px;">
<ul style="margin: 0px 1.571em 1.571em; padding: 0px; list-style-type: square;">
<li style="margin: 0px; padding: 0px 10px;">“Passive and Possessive—Pronouns for Pros” – Blog Article – 773 words</li>
<li style="margin: 0px; padding: 0px 10px;">“Two-Minute Drill: Coulda, Shoulda, Woulda, and More” – 706 words</li>
<li style="margin: 0px; padding: 0px 10px;"><em>Choose: Volume 1</em> – Copyediting – 20,000 words @ 10 percent – 2,000 words</li>
<li style="margin: 0px; padding: 0px 10px;">Style sheet for <em>Choose</em> – Copyediting – 531 words @ 25 percent – 133 words</li>
</ul>
<p style="margin: 0px 1.571em; padding: 0px;"><strong>Total: 3,612 words.</strong> Considering I&#8217;ve been hitting 1,500 words per week without really trying, I&#8217;m going to raise the bar to 2,000 words, despite leaving on a 3-week vacation on Monday. While that increase may not seem like a lot, had I not been editing <em>Choose, </em>would I have hit 1,500? I&#8217;d like to think so.</p>
<p style="margin: 0px 1.571em; padding: 0px;">
<p style="margin: 0px 1.571em; padding: 0px;">Raising the goal to 2,000 words will also give me the incentive to maintain two or three blog posts each week, as well as do some creative writing each week. I&#8217;d like to see that goal bumped up to 3,000 words, but I also know that spring (and summer) will eventually arrive, and I&#8217;ll be outdoors more, instead of in front of the computer all day.</p>
<h2>Short Grammar Quiz</h2>
<p style="margin: 0px 1.571em; padding: 0px;">Over the past couple weeks, I&#8217;ve collected a few examples of what not to do, as I&#8217;ve been reading various and sundry blogs. I&#8217;m going to show you some of those, and let you determine why I&#8217;ve selected them. If, by chance, you happen to recognize the snippet, please understand that in no way is my intent to disparage the authors or their blogs; simply to illustrate &#8220;real-life&#8221; examples of errors in grammar or punctuation. With that, take look at these and see if you can determine why I included them. Feel free to answer in the comments. Also, be warned: The errors are not all that difficult to spot; there are no &#8220;gotchas.&#8221; <img src='http://kestrelsaerie.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p style="margin: 0px 1.571em; padding: 0px;">
<ol>
<li>&#8230; prevent them from dieing &#8230;</li>
<li>You’ll commonly hear “bring the player, not the class”.</li>
<li>If someone is moving better then I [am]</li>
<li>some 3/32th inch elastic cord</li>
<li>The traffic to the server is increased massively since Christmas, it looks like there are no end of people</li>
<li>See if your a Canadian or &#8230; can count on always having on in your party</li>
</ol>
<p style="margin: 0px 1.571em; padding: 0px;">
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2718-1'> That&#8217;s rather an arbitrary figure, and may be too high; likewise, ten percent for copyediting may be too low, especially considering that it takes at least as long to edit as it does to compose. In fact, I originally posted that copyediting would count at 50 percent; however, I&#8217;ll stick with these ratios for now. <span class='footnotereverse'><a href='#fnref-2718-1' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/01/weekly-word-count-january-22/">Weekly Word Count: January 22</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/01/weekly-word-count-january-22/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Two-Minute Drill: Coulda, Shoulda, Woulda, and More</title>
		<link>http://kestrelsaerie.com/2010/01/twominute-drill-coulda-shoulda-woulda/</link>
		<comments>http://kestrelsaerie.com/2010/01/twominute-drill-coulda-shoulda-woulda/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 16:44:56 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[abbreviations]]></category>
		<category><![CDATA[e.g.]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[helping verbs]]></category>
		<category><![CDATA[i.e.]]></category>
		<category><![CDATA[two-minute drill]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2708</guid>
		<description><![CDATA[<p>Wouldn’t writing in English be so much easier if we could just write out words, or combinations of words, the way they sound? Instead of typing out <em>forget about it, </em>I could simply write <em>fuggedaboudit </em>and be done.</p>
<p>Of course, if I’m writing dialogue, I can do such things, if the character’s vernacular is such that he’s from the Lower&#8230;</p><p><a href="http://kestrelsaerie.com/2010/01/twominute-drill-coulda-shoulda-woulda/">Two-Minute Drill: Coulda, Shoulda, Woulda, and More</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Wouldn’t writing in English be so much easier if we could just write out words, or combinations of words, the way they sound? Instead of typing out <em>forget about it, </em>I could simply write <em>fuggedaboudit </em>and be done.</p>
<p>Of course, if I’m writing dialogue, I can do such things, if the character’s vernacular is such that he’s from the Lower East End or South Jersey. For example, here’s the classic line by Marlon Brando’s character, Terry,&nbsp; in <em>On the Waterfront </em>(1954): “I coulda been a contender. I coulda been somebody.” You can be sure the script does not say “could have been.”</p>
<p>Clearly, none of us is going to write “coulda” in normal prose, even though that’s how we often hear it said. No; instead, what we see is, “I <em>could of </em>been a contender” or “I <em>should of</em> left before it got ugly” or “I <em>would of</em> bought you that if I knew you wanted it.”</p>
<p>So what’s wrong there? They all <em>sound</em> right, when we speak them (quickly), but that’s exactly how people get into trouble: They write what they hear (or think they hear), instead of what is correct. But how do we know whether <em>could have </em>or <em>could of </em>is correct?</p>
<blockquote class="right"><p>Could, should, would require helping verbs, not a preposition!</p>
</blockquote>
<p><em>Could, should, </em>and <em>would </em>(as well as <em>have</em>) all belong to that group of words called “<a title="English Club: Helping Verbs" href="http://www.englishclub.com/grammar/verbs-what_classification-helping.htm">helping verbs</a>” (also known as <em>auxiliary verbs</em>)<em>.</em> Helping verbs are followed by either another helping verb (“could <strong>have</strong> seen”), a verb (“could <strong>see</strong>”), an adverb (“could <strong>barely</strong> see”), or a negative (“could <strong>not</strong> see”). </p>
<p>The word <em>of</em> is not a verb (nor is it a helping verb); it’s a preposition. And, because it is a preposition, it needs to be part of a prepositional phrase, and in the construction “could of been a contender” there is no prepositional phrase. </p>
<p>So to avoid confusion when using could/should/would, remember to keep your helping verbs close to each other, and away from that naughty preposition!</p>
<hr />
<blockquote class="left">&quot;Divorcé&quot; is the future imperfect form of &quot;fiancé&quot;</p></blockquote>
<p>Now, we’re not going to merely shift gears, we’re going to shift parts of speech as well. </p>
<p>Most of us know, I’m sure, that a formerly married woman is known as a <em>divorcée</em>. Similarly, most of us know a man’s intended bride is his <em>fiancée</em>. Unfortunately, not everyone is aware that the man to whom a woman is engaged to be married is her <em>fiancé</em>. That’s right: two genders, two words.<sup class='footnote'><a href='#fn-2708-1' id='fnref-2708-1'>1</a></sup></p>
<p>In case you’re wondering, <em>divorcé</em> is also a word, and indicates a divorced man. It’s the future imperfect from of <em>fiancé</em>.&nbsp; </p>
<hr />
<p>Today&#8217;s final bit is the distinction between the abbreviations &quot;i.e.&quot; and &quot;e.g.&quot;</p>
<p>Both are from Latin, but because both are so commonly used in English, they are not considered foreign words or terms, and are normally&nbsp;not italicized.<sup class='footnote'><a href='#fn-2708-2' id='fnref-2708-2'>2</a></sup></p>
<p>&quot;I.e.&quot; is probably the more common of the two (possibly because it&#8217;s misused more often?), is short for <em>id est, </em>and means, simply, &quot;that is.&quot; &quot;E.g.&quot; is short for <em>exempli gratia</em> (“for the sake of example”). These are abbreviations, so the periods after each letter are required; furthermore, use a comma on either side of them. Avoid using both in the same sentence.</p>
<blockquote style="margin-right: 0px" dir="ltr"><p>If the employee is on salary, i.e., paid by the week rather than the hour, the fee is $10.00.</p>
<p>The most common American beers are pilseners, e.g., Budweiser, Coors, and Miller.</p>
</blockquote>
<p dir="ltr">Finally, if you start a list with &quot;e.g.,&quot; there&#8217;s no need to end it with &quot;etc.&quot; (the abbreviation for <em>et cetera, </em>&quot;and so on&quot;), because the &quot;e.g.&quot; implies the list is not all-inclusive.</p>
<hr />
<p>Are there other words or word forms you see used improperly? Or are there some you aren’t sure about how to use properly? Post in the comments, or email me using the <a title="Kestrel's Aerie: Email Steve" href="http://kestrelsaerie.us/about/contact/">contact form</a> , and I’ll address them in a future article.</p>
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2708-1'> Incidentally, I’ve italicized the words to make them stand out; even though they are technically “foreign” words, coming to us from French, do not italicize them in normal prose. That’s another article for another day, by the way. <span class='footnotereverse'><a href='#fnref-2708-1' >&#8617;</a></span></li>
<li id='fn-2708-2'> I say &quot;normally not italicized,&quot; because some publishing houses, especially for scholarly texts, may dictate otherwise. But for what you and I use them for, use Roman type. <span class='footnotereverse'><a href='#fnref-2708-2' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/01/twominute-drill-coulda-shoulda-woulda/">Two-Minute Drill: Coulda, Shoulda, Woulda, and More</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/01/twominute-drill-coulda-shoulda-woulda/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Passive and Possessive&#8212;Pronouns for Pros</title>
		<link>http://kestrelsaerie.com/2010/01/passive-possessivemdashpronouns-pros/</link>
		<comments>http://kestrelsaerie.com/2010/01/passive-possessivemdashpronouns-pros/#comments</comments>
		<pubDate>Mon, 18 Jan 2010 21:07:07 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[pronouns]]></category>
		<category><![CDATA[punctuation]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2698</guid>
		<description><![CDATA[<p>How about some mad props for the alliterative title? Hopefully, it caught your attention and prompted you to read more. So without further ado….</p>
<p>First, let’s be sure we’re all on the same page with respect to what pronouns are. They are words we substitute for nouns, generally to avoid repeating the nouns each time we want to refer to&#8230;</p><p><a href="http://kestrelsaerie.com/2010/01/passive-possessivemdashpronouns-pros/">Passive and Possessive&mdash;Pronouns for Pros</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p>How about some mad props for the alliterative title? Hopefully, it caught your attention and prompted you to read more. So without further ado….</p>
<p>First, let’s be sure we’re all on the same page with respect to what pronouns are. They are words we substitute for nouns, generally to avoid repeating the nouns each time we want to refer to those people, places or things.</p>
<p>Pronouns are used in first–, second–, and third–person, and in singular and plural forms. They can be active and objective, or passive and subjective. </p>
<p>Before we get down to cases, let’s look at pronouns in tabular form: </p>
<table border="1" cellspacing="0" cellpadding="2" width="546">
<tbody>
<tr>
<td width="118" align="center">&nbsp;</td>
<td width="106" align="center"><strong>Subjective</strong></td>
<td width="108" align="center"><strong>Subjective <br />  Possessive</strong></td>
<td width="106" align="center"><strong>Objective</strong></td>
<td width="106" align="center"><strong>Objective <br />  Possessive</strong></td>
</tr>
<tr>
<td valign="top" width="118"><font size="2"><strong>1st-Person Singular</strong></font></td>
<td width="106" align="center"><font size="2">I</font></td>
<td width="108" align="center">my</td>
<td width="106" align="center"><font size="2"></font>me</td>
<td width="106" align="center"><font size="2"></font>mine</td>
</tr>
<tr>
<td valign="top" width="118"><font size="2"><strong>2nd-Person Singular</strong></font></td>
<td width="106" align="center"><font size="2"></font>you</td>
<td width="108" align="center"><font size="2"></font>your</td>
<td width="106" align="center"><font size="2"></font>you</td>
<td width="106" align="center"><font size="2"></font>yours</td>
</tr>
<tr>
<td valign="top" width="118"><font size="2"><strong>3rd-Person Singular</strong></font></td>
<td width="106" align="center"><font size="2"></font>he/she/it</td>
<td width="108" align="center"><font size="2"></font>his/her/its</td>
<td width="106" align="center"><font size="2"></font>him/her/it</td>
<td width="106" align="center"><font size="2"></font>his/hers/its</td>
</tr>
<tr>
<td valign="top" width="118"><font size="2"><strong>1st-Person Plural</strong></font></td>
<td width="106" align="center"><font size="2"></font>we</td>
<td width="108" align="center"><font size="2"></font>our</td>
<td width="106" align="center"><font size="2"></font>us</td>
<td width="106" align="center"><font size="2"></font>ours</td>
</tr>
<tr>
<td valign="top" width="118"><font size="2"><strong>2nd-Person Plural</strong></font></td>
<td width="106" align="center"><font size="2"></font>you</td>
<td width="108" align="center"><font size="2"></font>your</td>
<td width="106" align="center"><font size="2"></font>you</td>
<td width="106" align="center"><font size="2"></font>yours</td>
</tr>
<tr>
<td valign="top" width="118"><font size="2"><strong>3rd-Person Plural</strong></font></td>
<td width="107" align="center">they</td>
<td width="108" align="center">their</td>
<td width="106" align="center">them</td>
<td width="106" align="center">theirs</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<blockquote class="left"><p>Pronouns never, EVER have apostrophes.</p>
</blockquote>
<p>The first thing I want you to notice about the table above is this: There is <strong>no apostrophe</strong> in that table. Anywhere. There are few absolutes in this world, but here is one: <small><em><strong>PRONOUNS NEVER, EVER HAVE APOSTROPHES.</strong></em></small></p>
<p>Unlike pronouns, nouns generally use an apostrophe to indicate the possessive case:</p>
<blockquote><p>Tom’s book is on the table.</p>
<p>The book on the table is not Mary’s.</p>
<p>The cat’s toy is under the davenport.</p>
<p>New York’s skyline is one of the most recognizable in the world.</p>
</blockquote>
<p>Another thing you should note that is if we were to diagram these sentences<sup class='footnote'><a href='#fn-2698-1' id='fnref-2698-1'>1</a></sup>, each of the possessive nouns above would be identified as an adjective. That’s a confusing topic we’ll save for another day.</p>
<p>Now let’s substitute pronouns for the possessive nouns:</p>
<blockquote><p>His book is on the table</p>
<p>The book on the table is not hers.</p>
<p>Its toy is under the davenport.</p>
<p>Its skyline is one of the most recognizable in the world.</p>
</blockquote>
<p>If you’re comparing the sentences to the words as laid out in the table, you probably noticed that one of these things is not like the others. If you haven’t done that comparison, I’ll give you a moment to figure out which is different.</p>
<p>Hopefully, you determined the second sentence is the oddball. Why? Because in this case, the pronoun is the <em>objective </em>form. Remember, the classic form of the sentence in English is <em>Subject – verb – object. </em>The subject and object are nouns or pronouns: The subject performs an action (denoted by the verb), while the object has something done to it. (And just to complicate matters, when we make the object into a subject, we end up with <em>passive voice. </em>Yet another Topic To Be Addressed Later.)</p>
<p>However, I do want to address passive voice here at least in terms of pronoun use. Let’s look at a situation that occurs around my house each time my wife bakes: </p>
<blockquote><p>I eat the cookies.</p>
<p>Steve eats the cookies.</p>
<p>He ate the cookies.</p>
<p>The cookies were eaten by me.</p>
<p>The cookies are also eaten by her.</p>
</blockquote>
<p>In the first three sentences, &quot;the cookies&quot; are the object of my action (eating). The last two are classic examples of passive voice. The key here, if you must use passive voice (and it’s rarely wrong, just awkward), is to be sure you use the proper pronoun form. In the examples above, “the cookies” are the subject of the last two&nbsp;sentences; thus, the objective pronouns “me” and “her” are correct, rather than the subjective “I” and “she.”</p>
<blockquote class="right"><p>Never, ever join a subjective and an objective pronoun with a conjunction</p>
</blockquote>
<p>If you keep a mental copy of the table above in your head, you won’t find yourself <sup class='footnote'><a href='#fn-2698-2' id='fnref-2698-2'>2</a></sup> using such combinations as <em>her and I, she and him, he or us: </em>When joining pronouns with a conjunction, both (or all) pronouns must be the same type, either subjective or objective.</p>
<p>Of course, that doesn’t prevent the following:</p>
<blockquote><p>Me and her went to the movie.</p>
</blockquote>
<p><em>Shudder. Twitch.</em></p>
<p>If you’re going to use one or more pronouns as the subject of a sentence, use the subjective form(s). Similarly, if the pronouns are the objects of an action, use the objective forms. Don’t combine forms with a conjunction.</p>
<p>I hope this article has been enlightening, as well as helpful. If nothing else, perhaps we’ve saved a few more of our collective readers from future mistakes of our’s.<sup class='footnote'><a href='#fn-2698-3' id='fnref-2698-3'>3</a></sup></p>
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2698-1'> Don’t worry; I still have nightmares about the linguistics course I took in college, not to mention high school English: No diagramming here! <span class='footnotereverse'><a href='#fnref-2698-1' >&#8617;</a></span></li>
<li id='fn-2698-2'> Yes, pronoun forms ending with –self are another form, but not one I want to get into here; just keep in mind they are always objective. <span class='footnotereverse'><a href='#fnref-2698-2' >&#8617;</a></span></li>
<li id='fn-2698-3'> See what I did there? Don&#8217;t do it! <span class='footnotereverse'><a href='#fnref-2698-3' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/01/passive-possessivemdashpronouns-pros/">Passive and Possessive&mdash;Pronouns for Pros</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/01/passive-possessivemdashpronouns-pros/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Two-Minute Drill: Allude and Elude</title>
		<link>http://kestrelsaerie.com/2010/01/twominute-drill-allude-elude-2/</link>
		<comments>http://kestrelsaerie.com/2010/01/twominute-drill-allude-elude-2/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 19:02:28 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[allude]]></category>
		<category><![CDATA[elude]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[two-minute drill]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2672</guid>
		<description><![CDATA[<p><em>This post is the first in what I hope will be a series of short (two minutes to read) articles highlighting commonly confused or misused words.</em> </p>
<p>I was reading a blog article yesterday, and the following sentence caught my eye. Then it made me grit my teeth. Fortunately, I have a dentist appointment Thursday for a new crown. (Okay,&#8230;</p><p><a href="http://kestrelsaerie.com/2010/01/twominute-drill-allude-elude-2/">Two-Minute Drill: Allude and Elude</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p><em>This post is the first in what I hope will be a series of short (two minutes to read) articles highlighting commonly confused or misused words.</em> </p>
<p>I was reading a blog article yesterday, and the following sentence caught my eye. Then it made me grit my teeth. Fortunately, I have a dentist appointment Thursday for a new crown. (Okay, just kidding about the crown.) Here’s the offending statement:</p>
<blockquote><p>Why people find this concept so difficult to understand simply alludes me.</p>
</blockquote>
<p>You may be wondering why I didn’t include <em>allude</em> and <em>elude</em> in yesterday’s article on homophones. The simple answer is, they aren’t. Homophones, that is. Yes, they sound similar, but it’s a long way from “similar” to “identical.” The first syllable of <em>allude </em>is pronounced as “ah,” while the initial syllable of <em>elude </em>sounds like “eh.”</p>
<p>Having&nbsp;cleared that&nbsp;up, let’s<sup class='footnote'><a href='#fn-2672-1' id='fnref-2672-1'>1</a></sup> move on to the difference between the two words under discussion.</p>
<p><em>Allude</em> is a verb meaning “to refer (to)” while <em>elude</em> is a verb meaning “to evade.” Not even remotely close in meaning, are they? Then why do people continue to confuse them? I could construct a pretty elaborate theory on why it happens, but that would be a lengthy tangent we don’t need to explore here. </p>
<blockquote class="right"><p>People don&#8217;t take time to proofread and edit before they hit the &quot;publish&quot; or &quot;send&quot; button</p>
</blockquote>
<p>What I really think is that a lot of people (mostly bloggers, I’m sad to say) don’t take enough time to <a title="Kestrel's Aerie: The Importance of Proofing" href="http://kestrelsaerie.us/2008/10/brewing-baking-and-blogging-the-importance-of-proofing/">proofread</a> and edit before hitting the “publish” or “send” button. The unfortunate consequence is they come off appearing to be less knowledgeable and less authoritative than otherwise might be the case. Furthermore, when I see such egregious errors, it really throws off my ability to focus on the actual point of what I’m reading. </p>
<p>By way of analogy, imagine driving down the highway on a nice spring day, really enjoying the drive, when suddenly you have to swerve quickly to avoid a crate in the middle of the road. I don’t know about you, but I’d be a bit shaken by that. The same sort of thing happens when I see words like these misused. (Well, okay, my blood pressure doesn’t spike and my heart rate doesn’t climb, but you get the idea, I hope.)</p>
<p>While we’re talking about <em>allude,</em>&nbsp; we should probably bring in its noun form, <em>allusion, </em>and the similar-sounding (but again, not homophonic) <em>illusion.</em><sup class='footnote'><a href='#fn-2672-2' id='fnref-2672-2'>2</a></sup> An <em>allusion </em>is a (possibly vague or veiled) reference to something, while an <em>illusion</em> is an act of deceiving, or a misleading image presented to one’s vision. </p>
<p>Once again, careful proofreading should catch errors involving these words, as long as you know which is the correct one in the first place. But that’s why you’re reading this!</p>
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2672-1'> Contrary to my advice in yesterday’s article, I can use “let’s” because I know the difference between “lets” and “let’s.” However, I’m a professional. Kids, don’t try this at home. <span class='footnotereverse'><a href='#fnref-2672-1' >&#8617;</a></span></li>
<li id='fn-2672-2'> In case you’re wondering, “illude” is not a word, but “elusion” is the act of eluding. <span class='footnotereverse'><a href='#fnref-2672-2' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/01/twominute-drill-allude-elude-2/">Two-Minute Drill: Allude and Elude</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/01/twominute-drill-allude-elude-2/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Grammar Potpourri: Homophones</title>
		<link>http://kestrelsaerie.com/2010/01/grammar-potpourri-homophones/</link>
		<comments>http://kestrelsaerie.com/2010/01/grammar-potpourri-homophones/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 22:13:08 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[homophones]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2659</guid>
		<description><![CDATA[<p>When I <a title="Kestrel's Aerie: &#34;English Comp 101&#34;" href="http://kestrelsaerie.us/2009/09/english-comp-101-cliff-notes-version/">first discussed grammar and punctuation</a> back in mid-September (was it <em>that</em> long ago?), many of you commented about things I hadn’t included. Today, I’m going to address some of those. If there are others I don’t discuss today, rest assured they will be covered Some Day Soon<sup>.TM</sup></p>
<p>Before I list some of&#8230;</p><p><a href="http://kestrelsaerie.com/2010/01/grammar-potpourri-homophones/">Grammar Potpourri: Homophones</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p>When I <a title="Kestrel's Aerie: &quot;English Comp 101&quot;" href="http://kestrelsaerie.us/2009/09/english-comp-101-cliff-notes-version/">first discussed grammar and punctuation</a> back in mid-September (was it <em>that</em> long ago?), many of you commented about things I hadn’t included. Today, I’m going to address some of those. If there are others I don’t discuss today, rest assured they will be covered Some Day Soon<sup>.TM</sup></p>
<p>Before I list some of the more commonly confused homophone pairs (and triplets), I want to be sure we all understand the differences among homophones, homonyms, and homographs. <a title="Copyediting: &quot;Homonyms, homophones, and homographs&quot;" href="http://www.copyediting.com/wordpress/?p=265">An excellent article at the Copyediting blog</a> goes into more detail, but since we have a lot to cover today, let’s keep this discussion relatively short.</p>
<ul>
<li><em>Homophones</em> are words that sound alike (or identical) but are spelled differently; e.g., <em>their</em>, <em>there</em>, and <em>they’re</em>.</li>
<li><em>Homonyms </em>are words that are spelled the same, sound the same, but have different meanings; e.g., the <em>right</em> side of the road, and the <em>right</em> to peacefully assemble. Often, as in the preceding example, the words are different parts of speech (adjective and noun, respectively, in this case); but they can be the same part of speech. For instance, <em>bank </em>of a river and savings <em>bank</em> are both nouns.</li>
<li><em>Homographs</em> are words with the same spelling, but may not sound the same: The verb <em>refuse</em> is accented on the second syllable, while the noun <em>refuse</em> is accented on the first.</li>
</ul>
<p>So what are some commonly misused homophones? Obviously the example I gave above of <em>their</em>, <em>there</em>, and <em>they’re </em>is a classic one. Compounding the error, how often have you see something like these abominations:</p>
<ul>
<li>“They had to return the money because it wasn’t<em> there’s</em>.” Ouch! Not only the wrong form of <em>their, </em>but now the writer has tried to make a possessive with the apostrophe and “s.” (If you can give me a proper example of <em>their’s, </em>I’ll…well, you can’t, so never mind.)</li>
<li>Believe it or not, I actually saw “they’re’s” the other day. I wish I’d thought to copy the entire sentence. Yes, really: <em>two</em> apostrophes in the same word! (The intended word was “there’s,” the contracted form of “there is.”)</li>
</ul>
<p>Here are some more homophones that are frequently misused (or abused).<sup class='footnote'><a href='#fn-2659-1' id='fnref-2659-1'>1</a></sup></p>
<ul>
<li>The word <em>to</em> is a preposition; <em>too</em> is an adverb meaning “also.” And <em>two </em>is a number (generally, an adjective, in case you’re wondering) which, while rarely substituted for either <em>to </em>or <em>too, </em>is too often replaced with one of the other forms.</li>
<li><em>Wear </em>is a verb, <em>ware</em> is a noun, and <em>where </em>isn’t really pronounced like the other two (and it can be an adverb, conjunction, or noun).<sup class='footnote'><a href='#fn-2659-2' id='fnref-2659-2'>2</a></sup> Unfortunately, this particular situation gets even more muddled when careless writers misspell “wear” or “where” as <em>were.</em> Or vice versa. “But I spell-checked it!”</li>
<li>&nbsp;<em>Carat, caret,</em> and <em>carrot.</em>Very rarely is the third form substituted for either of the other two, but when it happens, the result is usually hilarious. A <em>carat</em> is a measure of fineness of gold or weight of gems<sup class='footnote'><a href='#fn-2659-3' id='fnref-2659-3'>3</a></sup>, while a <em>caret </em>is a typographical mark (^) indicating an insertion point.</li>
<li><em>Alter </em>means “change,” while <em>altar</em> is where marital problems begin.<sup class='footnote'><a href='#fn-2659-4' id='fnref-2659-4'>4</a></sup></li>
<li>If you’re waiting with <em>baited </em>breath, just stop: It smells like worms. Instead, try <em>bated </em>breath, which means restrained or reduced.</li>
<li><em>Dual</em> means two or twin; <em>duel </em>is a formal combat between two persons.<sup class='footnote'><a href='#fn-2659-5' id='fnref-2659-5'>5</a></sup></li>
<li>Once more, for good measure: <em>Its</em> is a possessive pronoun, like <em>his, hers,</em> and <em>ours. It’s</em> is a contraction of “it is.” There is a very simple way to avoid confusing the two: always try to write out “it is.” If it doesn’t work, use <em>its. </em>If it does work, <strong>leave it alone.</strong><em> “</em>I wanted to put the picture in <strong>it is</strong> place.” In other words, eschew the apostrophe. Or risk having your editor chew on you.</li>
<li>On the other hand, <em>lets </em>is a verb meaning “allows” or “leases.” <em>Let’s </em>is a contraction for “let us.” </li>
<li><em>Peak, peek,</em> and <em>pique. </em>No, that third form is <strong>not</strong> pronounced “pee-KAY.” All three can be verbs: “The Cardinals <strong>peaked</strong> [rose to their highest point] going into the playoffs.” “John <strong>peeked</strong> [took a quick or surreptitious look] into the nursery to be sure the baby was asleep.” “The descriptions of 3D-TV from the Consumer Electronics Show <strong>piqued</strong> [raised or aroused] my interest.” The usual confusion with these words is to use peaked in place of piqued.</li>
<blockquote class="right"><p>Bridal has to do with getting married; bridle has to do with controlling a horse. DO NOT make the obvious joke</p>
</blockquote>
<li><em>Bridal</em> has to do with getting married; <em>bridle </em>has to do with controlling a horse. Guys, don’t even think of making the obvious joke.</li>
<li>Speaking of horses, <em>reins</em> are attached to a bridle; <em>rains</em> are what fall in Spain (mainly in the plain); <em>reigns </em>are what monarchs are known for.</li>
<li>Following the current stream of consciousness, a <em>plain</em> is a (generally) flat, fallow area of land, while a <em>plane </em>is a conveyance, woodworking tool, cooking gadget, or geometrical construct. “Plain Jane” is rather homely, but “plane Jane” is probably a pilot.</li>
</ul>
<p>I could go on, and on, and on, and on. But I think my time is up for this round. Let me summarize by reminding you that your spell-checker won’t save you from homophonic crimes against grammar, but a good dictionary will. I know there are literally hundreds of homophones I could present here, but what are some I didn’t address, which you find particularly egregious?</p>
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2659-1'> I was going to say “confused” instead of “misused,” but I think that’s cutting the writer way too much slack. If you are going to write, write <strike>right</strike> correctly! <span class='footnotereverse'><a href='#fnref-2659-1' >&#8617;</a></span></li>
<li id='fn-2659-2'> I’ve found that if I can’t name the part of speech of word right off the bat, chances are at least one form of it is an adverb. <span class='footnotereverse'><a href='#fnref-2659-2' >&#8617;</a></span></li>
<li id='fn-2659-3'> Commonly abbreviated <em>K </em>or <em>kt, </em>from the alternative spelling <em>karat, </em>when used with gold, but <em>ct </em>when referring to gems: 24K gold filigree, but 1.5-ct. diamond. <span class='footnotereverse'><a href='#fnref-2659-3' >&#8617;</a></span></li>
<li id='fn-2659-4'> I shouldn’t have to explain that was a joke; I’ve been happily married for more than 35 years. <span class='footnotereverse'><a href='#fnref-2659-4' >&#8617;</a></span></li>
<li id='fn-2659-5'> In World of Warcraft, “duel-spec” should only mean a non-Arena, non-Battleground PvP spec; “dual-spec” is the one that costs 1000 gold. <span class='footnotereverse'><a href='#fnref-2659-5' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/01/grammar-potpourri-homophones/">Grammar Potpourri: Homophones</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/01/grammar-potpourri-homophones/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Capital Ideas</title>
		<link>http://kestrelsaerie.com/2010/01/capital-ideas/</link>
		<comments>http://kestrelsaerie.com/2010/01/capital-ideas/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 17:48:10 +0000</pubDate>
		<dc:creator>Kestrel</dc:creator>
				<category><![CDATA[Writing and Editing]]></category>
		<category><![CDATA[capitalization]]></category>
		<category><![CDATA[grammar]]></category>

		<guid isPermaLink="false">http://kestrelsaerie.us/?p=2624</guid>
		<description><![CDATA[<p>As I kick off a new series of grammar and punctuation articles to kick off the new year, I figured we might as well start at the top. Based on a suggestion on Twitter from <a title="Tami Moore's blog" href="http://tamimoore.com">Tami</a>, aka <a rel="nofollow" target="_blank" href="http://twitter.com/tami_moore">@tami_moore</a>, I’m going to tackle capitalization: when, how, and where.</p>
<h3>The Rules</h3>
<p>There are some conventions&#8230;</p><p><a href="http://kestrelsaerie.com/2010/01/capital-ideas/">Capital Ideas</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></description>
			<content:encoded><![CDATA[<p>As I kick off a new series of grammar and punctuation articles to kick off the new year, I figured we might as well start at the top. Based on a suggestion on Twitter from <a title="Tami Moore's blog" href="http://tamimoore.com">Tami</a>, aka <a rel="nofollow" target="_blank" href="http://twitter.com/tami_moore">@tami_moore</a>, I’m going to tackle capitalization: when, how, and where.</p>
<h3>The Rules</h3>
<p>There are some conventions to be followed when using capitals. As far as I can tell, there are no differences between American and British usage; however, if any of my non-American readers are aware of any, please let me know. One thing to keep in mind is that for all the rules below, in general I’m talking about initial capital letters; i.e., the first letter in a word. If I address ALL CAPS, I’ll make that quite explicit.</p>
<p>1. <strong>Capitalize the first word in a sentence.</strong></p>
<p>2. <strong>Capitalize proper nouns.</strong> “Proper nouns” include names of people (Steve, Kestrel) and places (Rapid City, England, Mount Rushmore). </p>
<ul>
<li><strong>Capitalize titles when used as a form of address or part of a name.</strong> Senator Thune, Father O’Malley, Pastor Jones, but “the senator” or “the pastor.”</li>
<li><strong>Capitalize full forms of university degrees. </strong>This is a subset of the previous rule. Bachelor of Arts or Master of Science, but “bachelor’s degree” or “master’s degree”</li>
</ul>
<p>3. <strong>Capitalize the “key words” in a title.</strong> Or not. This is a matter of <em>style, </em>and as such, is somewhat open to interpretation. I put this as a “rule” because the question will come up (in fact, it did, from <a title="Steampanku website" href="http://steampanku.wordpress.com/">Krizzlybear</a> and <a rel="nofollow" target="_blank" href="http://twitter.com/JustAnna">@JustAnna</a>), so I want to address this when we talk about specifics below.</p>
<p>4. <strong>Capitalize other stuff as appropriate</strong>. Such as abbreviations. But not all of them. </p>
<h3>Getting Down to Cases</h3>
<p>(See what I did there?)</p>
<h4>Capitalize the first word in a sentence.</h4>
<p>The only people who get this wrong are lazy, or e.e. cummings (but he’s a poet, and poetry is a completely different species). If <em>you</em> break this rule, I’m going to assume you missed the shift key. (Caveat: If you get to be as famous as e.e. cummings, you, too, may do any thing you damn well please with regard to style. Until then, however, it&#8217;s probably best if you follow the rules. Such as they are.)</p>
<p>Nevertheless, there is a special case we should address: the first letter following a colon. In this case, the rule is quite simple: If what follows the colon forms a complete sentence, then capitalize the first word. Look closely at the preceding two sentences: Each of them has a colon. In the first, what follows the colon is, in effect, a <em>sentence fragment, </em>hence, no cap. In the second, the colon separates two complete sentences; thus, a capital is used to start the part following the colon.<sup class='footnote'><a href='#fn-2624-1' id='fnref-2624-1'>1</a></sup> Incidentally, the only time you capitalize after a <em>semicolon</em> is if the word is a proper noun. </p>
<blockquote class="right"><p>After a colon, capitalize the first letter only if the words form a complete sentence.</p>
</blockquote>
<h4>Capitalize proper nouns.</h4>
<p>If the preceding rule was the first one we learned, this one was second. Or vice versa. About the only time names aren’t capitalized when they should be (which is <em>always</em>) is the result of a typo. Again, though, there are some areas where people just aren’t sure whether to use a capital. </p>
<ul>
<blockquote class="left">Capitalize President Obama, but not &quot;the president&quot;</p></blockquote>
<li>A title preceding a proper name requires a capital: Senator Thune, Queen Elizabeth II, Mayor Bloomberg. However, if you’re discussing the senator, the queen, or the mayor, lowercase is the way to go.<sup class='footnote'><a href='#fn-2624-2' id='fnref-2624-2'>2</a></sup><sup>, </sup><sup class='footnote'><a href='#fn-2624-3' id='fnref-2624-3'>3</a></sup></li>
<li>The formal names of university or college degrees are capitalized, such as Master of Science or Doctor of Philosophy. But don’t capitalize master’s degree in history or bachelor’s in political science. And then there is my graduate degree, properly called Master of Business Administration. Yeah, I agree: “MBA” is so much easier. </li>
<blockquote class="right"><p>The Internet and the Web are places, just as the Matrix is. Caps, please!</p>
</blockquote>
<li>A few specific cases: The Internet is a “great big place” but it’s still a place, so capitalize it. Similarly, the Web is a shortened alternative, so if you’re using it to refer to the Internet, capitalize it as well. However, “website” can refer to any of millions of places on the Web, so it’s a nonspecific, uncapitalized noun.<sup class='footnote'><a href='#fn-2624-4' id='fnref-2624-4'>4</a></sup></li>
<li>And finally, Earth, Moon and Sun. Or are they the earth, the moon, and the sun? The dirt you plant flowers in is earth, or contains earth, which is a generic term for ground. When discussing our home planet, however, things get a bit more confusing. If you’re planning a trip from Earth (or the Earth) to Mars, Earth is almost always seen capitalized. But if you’re talking about earth’s escape velocity, you’ll see the word capitalized sometimes, and sometimes not. My <em>personal preference</em> is to capitalize Earth when I’m referring to the planet, without the preceding “the.” And to be consistent, our Sun and our Moon (but not the sun or the moon) should be capitalized, but that’s even less common. (And why is it “the earth”? We don’t talk about “the Saturn” or “the Mars.” The answer of course, is that “earth” is a synonym for “world.”) Isn’t English wonderful? </li>
</ul>
<h4>Capitalize “key words” in a title.</h4>
<p>Hoo boy…this is probably the area where the most questions arise. Each time I asked friends if they had questions about capitalization (and in Tami’s original tweet suggesting this topic), this question was asked. As I stated at the top, determining how to capitalize titles is a stylistic decision. <a title="Grammar Girl" href="http://grammar.quickanddirtytips.com/">Grammar Girl</a> has a good, <a title="Grammar Girl: Title Caps" href="http://grammar.quickanddirtytips.com/title-caps.aspx">short podcast on the topic</a>. The extremes, of course, are to treat a title as a sentence and capitalize only the first letter, to capitalizing the first letter of each word, to CAPITALIZING EVERY LETTER IN THE TITLE. That last may be fine for the cover of a book, but it’s a bit much for day-to-day writing, methinks.</p>
<blockquote class="left"><p>For Titles of Creative Works, Pick a Style and Stick With It</p>
</blockquote>
<p>So, let’s address the middle case, and the exceptions to this “rule.” Most of us were probably taught in school to capitalize all the words in a title except articles (a, an, the) and the prepositions “for” and “of.” The exceptions to <em>that,</em> however, are when such words are the first or last words of the title. According to writers.com <a title="Writers.com tips: Title Capitalization" href="http://www.writers.com/tips_titles.html">tips for title capitalization</a>:</p>
<blockquote><p>The U.S. Government Printing Office Style Manual offers one easy style: &quot;Capitalize all words in titles of publications and documents, except a, an, the, at, by, for, in, of, on, to, up, and, as, but, it, or, and nor.&quot;</p>
</blockquote>
<p>That’s good enough for me!</p>
<p><strong>But what about subtitles?</strong> What about subordinate elements such as sections, paragraphs, chapters, and the like? You can apply the same rules as for main titles (such as they are), or you can use a different style entirely. For example, for my blog (at least from this point forward) I intend to use the GPO style for article titles. But subsections may (and as is the case in this article) get an entirely different treatment. The most important thing to remember is to <em>be consistent within each type of title in a given document.</em> Not that anyone will break your fingers if you aren’t, but it will certainly give your work a more polished and professional appearance if you do maintain that consistency.</p>
<h4>Capitalize other stuff as appropriate.</h4>
<p>That’s nice and specific, isn’t it? Let’s look at abbreviations, as an example. <em>Generally speaking </em>(and please note the emphasis as connoted by the italics), if something is capitalized when written out, its abbreviation is similarly capitalized. If it’s not normally capitalized, don’t capitalize the abbreviation.</p>
<ul>
<li><strong>a.m. and p.m.</strong> These are abbreviations for ante meridiem and post meridiem, Latin terms for before and after noon, respectively. They are not capitalized.<sup class='footnote'><a href='#fn-2624-5' id='fnref-2624-5'>5</a></sup> Thus, 8:00 A.M. (or 8:00 AM) is incorrect. (So, too, is 8:00 am.) Incidentally (and I’m going to hate myself later for putting this here, because I won’t be able to find it later), noon and midnight are not capitalized unless they are the first word of a sentence. <em>*sigh* </em>And as long as we’re on the topic, try to avoid 12:00 a.m. or 12:00 p.m. Instead, use midnight and noon, respectively.<sup class='footnote'><a href='#fn-2624-6' id='fnref-2624-6'>6</a></sup> Look at that: A whole post compressed into one paragraph and two footnotes. The things I do for you, dear readers! </li>
<li><strong>State abbreviations</strong>. In the United States (U.S. or US; I much prefer the former, but USA over U.S.A. Once again, stylistic convention, but be consistent!), there are almost as many ways to abbreviate state names as there are states.<br /> <br />
<blockquote class="left">
<p>Reserve post office abbreviations for envelopes; use 3-5 letter state abbreviations elsewhere, if you must abbreviate.</p>
</blockquote>
<ul>
<li>Take my home state of California, for instance: Cal., Calif., or, per the U.S. Postal Service, CA. <em>N.B.: “Cali” is not, never has been, and never will be an acceptable shortening of the name of the state of California.</em><sup class='footnote'><a href='#fn-2624-7' id='fnref-2624-7'>7</a></sup> Ahem…where was I? Oh, yes…. </li>
<li>The two-letter postal abbreviations for states (and Canadian provinces) have both letters capitalized; e.g., AB (Alberta), BC (British Columbia), CA (California). Postal abbreviations do not have periods at the end; however, it might be acceptable to abbreviate some states such as Ca. or Co. (Of course, an abbreviation for Canada is Ca. and for county, Co. So why confuse matters?) </li>
<li>Finally, while SD is the postal abbreviation for South Dakota, S.D. is perfectly acceptable as well (similarly, N.C., N.D., S.C., R.I., etc.). Generally, postal abbreviations should be reserved for envelopes; other writing should use more conventional abbreviations, if you must abbreviate.</li>
</ul>
</li>
<li><strong>Multi-word abbreviations</strong>. Up above, I mentioned a.m. and p.m., and alluded to U.S. vs. US. Note there is no space after the periods in an abbreviation. This of course begs the question, are periods required in abbreviations? Short answer: It depends. Once again, it’s a stylistic choice. The <em>New York Times, </em>for example, abbreviates National Football League as N.F.L., which, when I read it, sounds like “enn…eff…ell.” “NFL,” on the other hand, which is how it’s abbreviated everywhere else that I know of, sounds like “eneffell.” Similarly, to me, U.S.A. and USA sound like “You. Ess. Ay.” and “YouEssAy,” respectively. But that’s just me. Once again, take your pick, but be consistent. <em>Consistency counts!</em> </li>
</ul>
<h3>Are we done yet?</h3>
<p>I hope so, but I doubt it. I’m sure I’ve left out everything you’ve wondered about capitalization, and included only those items that make you go, “Well, DUH!” Ohh…see? What about CAPS FOR EMPHASIS? I realize that in text chat, this is a simple convention to observe. But in serious (or even not-so-serious) writing, realize we live in the age of computers: It’s not that hard to hit Control-I (or Command-I, Mac users) to <em>italicize for emphasis.</em><sup class='footnote'><a href='#fn-2624-8' id='fnref-2624-8'>8</a></sup></p>
<p>If there are other areas of capitalization I omitted, or if you want to take issue with my position on any of these, let’s discuss in the comments!</p>
<div class='footnotes'>
<div class='footnotedivider'>__________<br />Notes:</div>
<ol><font size='2' color='#243355'>
<li id='fn-2624-1'> No doubt I’ll use this same paragraph when I talk about colons and semicolons in a future article. <span class='footnotereverse'><a href='#fnref-2624-1' >&#8617;</a></span></li>
<li id='fn-2624-2'> In the UK, is it preferred to capitalize “Queen” when speaking specifically about Queen Elizabeth? Someone enlighten me, please. <span class='footnotereverse'><a href='#fnref-2624-2' >&#8617;</a></span></li>
<li id='fn-2624-3'> Stylistically, some writers prefer to capitalize “the President” when speaking specifically about the president of the United States; however, it’s notable that almost every noun in the U.S. Constitution is capitalized, in the custom of the time it was originally penned. On the other hand, it can be argued the form in the Constitution is the full formal title of the office. <span class='footnotereverse'><a href='#fnref-2624-3' >&#8617;</a></span></li>
<li id='fn-2624-4'> Reference: <a title="http://grammar.quickanddirtytips.com/Capitalizing-Proper-Nouns.aspx" href="http://grammar.quickanddirtytips.com/Capitalizing-Proper-Nouns.aspx">http://grammar.quickanddirtytips.com/Capitalizing-Proper-Nouns.aspx</a> <span class='footnotereverse'><a href='#fnref-2624-4' >&#8617;</a></span></li>
<li id='fn-2624-5'> Actually, you can capitalize them, without periods, if you use small capitals. If you can do that faster than typing “a.m.” or “p.m.” though, more power to you! <span class='footnotereverse'><a href='#fnref-2624-5' >&#8617;</a></span></li>
<li id='fn-2624-6'> Reference: <a title="http://grammar.quickanddirtytips.com/daylight-saving-time.aspx" href="http://grammar.quickanddirtytips.com/daylight-saving-time.aspx">http://grammar.quickanddirtytips.com/daylight-saving-time.aspx</a> <span class='footnotereverse'><a href='#fnref-2624-6' >&#8617;</a></span></li>
<li id='fn-2624-7'> On the other hand, “Frisco” is perfectly acceptable as a substitute for “San Francisco,” but only if you live, or have lived, in Southern California, and preferably in the cities of Los Angeles or San Diego, or Orange County. <span class='footnotereverse'><a href='#fnref-2624-7' >&#8617;</a></span></li>
<li id='fn-2624-8'> I’m using Windows Live Writer on my Mac, so I have to use Ctrl-I, and it’s hard to get back into that habit, believe me! <span class='footnotereverse'><a href='#fnref-2624-8' >&#8617;</a></span></li>
<p></font></ol>
</div>
<p><a href="http://kestrelsaerie.com/2010/01/capital-ideas/">Capital Ideas</a> is a post from: <a href="http://kestrelsaerie.com">Kestrel&#039;s Aerie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kestrelsaerie.com/2010/01/capital-ideas/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/


Served from: kestrelsaerie.com @ 2010-09-07 13:10:13 -->