{"id":61,"date":"2007-06-29T11:11:47","date_gmt":"2007-06-29T18:11:47","guid":{"rendered":"http:\/\/www.bspcn.com\/2007\/06\/29\/do-you-make-these-mistakes-when-you-write\/"},"modified":"2007-06-29T11:11:47","modified_gmt":"2007-06-29T18:11:47","slug":"do-you-make-these-mistakes-when-you-write","status":"publish","type":"post","link":"http:\/\/localhost\/wordpress\/2007\/06\/29\/do-you-make-these-mistakes-when-you-write\/","title":{"rendered":"Do You Make These Mistakes When You Write?"},"content":{"rendered":"
Written by Brian Clark<\/a><\/p>\n <\/p>\n It’s time once again to review those nasty errors that damage our credibility when we write. Not normally a fun task, but absolutely necessary. I promise to keep you amused to diminish the pain (or at least I’ll give it a shot).<\/p>\n As with the last time we explored grammatical errors<\/a>, I feel compelled to mention that copywriting and blogging should be conversational and engaging, and breaking formal grammatical and spelling conventions can often be a good thing. Every time I see a comment complaining about something like, oh, I don’t know? the improper use of an ellipsis or one-sentence paragraphs, I shake my head with sadness.<\/p>\n They just don’t get it.<\/p>\n Outside of specific professional or academic contexts, writing with a personal style that makes it easier on the reader<\/em> is more important than pleasing Strunk and White<\/a>. That said, I also believe you have to know the rules in order to break them. Plus, there are some errors that you’ll never convince anyone that you did intentionally in the name of style (outside of a joke), and even then some people will still assume you’re dumb.<\/p>\n So, let’s take a look at some more of those types of glaring errors that you never want to make. Thanks to reader suggestions and the aforementioned Messrs. Strunk and White, here are seven more<\/em> common mistakes that can diminish the shine and credibility of your writing.<\/p>\n This one drives a lot of people crazy, including me. In fact, it’s so prevalent among bloggers that I once feared I was missing something, and somehow “loose” was a proper substitute for “lose” in some other English-speaking countries. Here’s a hint: it’s not.<\/p>\n If your pants are too loose<\/em>, you might lose<\/em> your pants.<\/p>\n<\/blockquote>\n One of the most common causes of grammatical pain is the choice between “me” and “I.” Too often people use “I” when they should use “me,” because since “I” sounds stilted and proper, it must be right, right? Nope.<\/p>\n The easy way to get this one right is to simply remove the other person from the sentence and then do what sounds correct. You would never say “Give I a call,” so you also wouldn’t say “Give Chris and I a call.” Don’t be afraid of me<\/em>.<\/p>\n And whatever you do, don’t punt and say “myself” because you’re not sure whether “me” or “I” is the correct choice. “Myself” is only proper in two contexts, both of which are demonstrated below.<\/p>\n Many consider Chris a punk, but I myself tolerate him. Which brings me to ask myself, why?<\/p>\n<\/blockquote>\n This one slips under the radar a lot, and I’ll bet I’ve screwed it up countless times. It boils down to the fact that things are logically different from<\/em> one another, and using the word “than” after different is a grammatical blunder.<\/p>\n This vase is different from<\/em> the one I have, but I think mine is better than<\/em> this one.<\/p>\n<\/blockquote>\n Basically, you use an apostrophe in two cases:<\/p>\n If still in doubt, leave the apostrophe out. It causes more reader confusion to insert an apostrophe where it doesn’t belong than it does to omit one. Plus, you can always plead the typo defense if you leave an apostrophe out, but you look unavoidably dumb when you stick one where it doesn’t belong.<\/p>\n Back when I talked about bullet points<\/a>, one of the tips involved keeping each bullet item in parallel by beginning with the same part of speech. For example, each item might similarly begin with a verb like so:<\/p>\n When writing a list of items in paragraph form, this is even more crucial, and failing to stay in parallel can result in confusion for readers and scorn from English majors. Check out this non-parallel list in a sentence:<\/p>\n Over the weekend, Kevin bought a new MacBook Pro online, two software programs, and arranged for free shipping.<\/p>\n<\/blockquote>\n Do you see the problem? If not, break the list into bullet points and it becomes clear:<\/p>\n Over the weekend, Kevin:<\/p>\n Stick the word “ordered” in front of “two software programs” and you’re in parallel. Your readers will subconsciously thank you, and the Grammar Nazis won’t slam you.<\/p>\n Ah, Latin? you’ve just gotta love it. As antiquated as they might seem, these two little Latin abbreviations are pretty handy in modern writing, but only if you use them correctly.<\/p>\n The Latin phrase id est<\/em> means “that is,” so i.e. is a way of saying “in other words.” It’s designed to make something clearer by providing a definition or saying it in a more common way.<\/p>\n Copyblogger has jumped the shark, i.e., gone downhill in quality, because Brian has broken most of his New Year’s resolutions<\/a>.<\/p>\n<\/blockquote>\n The Latin phrase exempli gratia<\/em> means “for example”, so e.g. is used before giving specific examples that support your assertion.<\/p>\n Copyblogger has jumped the shark because Brian has broken most of his New Year’s resolutions, e.g., promising not to say “Web 2.0<\/a>,” “linkbait<\/a>,” or “jumped the shark” on the blog in 2007.<\/p>\n<\/blockquote>\n Please don’t do this:<\/p>\n I should of<\/em> gone to the baseball game, and I could of<\/em>, if Billy would of<\/em> done his job.<\/p>\n<\/blockquote>\n This is correct:<\/p>\n I should have<\/em> gone to the baseball game, and could have<\/em>, if Billy would have<\/em> done his job.<\/p>\n<\/blockquote>\n Why do people make this mistake?<\/p>\n They could’ve<\/em>, should’ve<\/em>, would’ve<\/em> been correct, except that the ending of those contractions is slurred when spoken. This creates something similar to a homophone, i.e., a word that is pronounced the same as another word but differs in meaning, e.g., of<\/strong>, which results in the common grammatical mistake of substituting of<\/em> for have<\/em>.<\/p>\n Ain’t this been fun?<\/p>\n","protected":false},"excerpt":{"rendered":" Written by Brian Clark It’s time once again to review those nasty errors that damage our credibility when we write. Not normally a fun task, but absolutely necessary. I promise to keep you amused to diminish the pain (or at least I’ll give it a shot). As with the last time we explored grammatical errors, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[],"tags":[],"_links":{"self":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/posts\/61"}],"collection":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/comments?post=61"}],"version-history":[{"count":0,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/posts\/61\/revisions"}],"wp:attachment":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/media?parent=61"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/categories?post=61"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/tags?post=61"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}1. Loose vs. Lose<\/h3>\n
\n
2. Me, Myself, and I<\/h3>\n
\n
3. Different than vs. Different from<\/h3>\n
\n
4. Improper Use of the Apostrophe<\/h3>\n
\n
5. Parallelism<\/h3>\n
\n
\n
\n
\n
6. i.e. vs. e.g.<\/h3>\n
\n
\n
7. Could of, Would of, Should of<\/h3>\n
\n
\n