this is supposed to be a document that helps analysis/strategy article writers to not make common errors and how to fix them if/when they occur One of the most important parts of writing for any medium actually begins after the final period has been placed. Many of the greatest, most coherent and well-flowing speeches, essays and even song lyrics ever written have been edited and re-edited a number of times, looked over by numerous different eyes and influenced by several different perspectives. This take on writing can easily be applied to Smogon's strategy analyses and articles. A public internet forum is a fantastic way for a community to collectively look over a given article or analysis, and to both identify and correct errors committed in many initial attempts at a solid strategy article or analysis. Here are a few of the more common errors you should be on the lookout for. Opening Sentences A great analysis or article naturally starts with a great introductory sentence. You want to pull your readers in from the very beginning, and let them know that your writeup is intelligently written, has somewhere to go, and will be enjoyable to read from start to finish. For an example: "A good pokemon team has a mix of offensive and defensive pokémon that compliment one another and pose a constant threat to the opposing team." We can do better than this, right? How about: "When building a pokemon team, you must first have a central idea in your mind about what you want to accomplish, and then think about which pokemon will help you accomplish that goal in the most effective manner possible." Both of those sentences are admittedly short and out of context (one where the tital of the writeup would be "How to make an effective team" or something), but you can see how the latter has a little more life to it and makes you want to read on more than the former. A good opening paragraph should set the tone for the rest of the writeup, and your personality—which I will touch upon later—should be at least somewhat apparent from the very first sentence. Pretention You don't have to use big words to sound knowledgeable about something. An example: "Garchomp is very prevalent in this torridly-paced metagame due to how skillfully said pokemon boasts a Choice Scarf, superb Base Attack and an impressive array of moves that can threaten even the staunchest of defenses." No. You may think you sound smart, but most readers will either wonder why you chose such "big" words or wonder whether you realize how pompous your writing style is. An example of the above sentence with less pretention: "Garchomp is very prevalent in today's fast-paced metagame because of how well it can use a Choice Scarf, its great attacking stats and Outrage, Earthquake and Fire Blast to pose a huge threat to any pokemon team." I don't feel that sentence is just a "dumbed-down" version of the former sentence—it still gets the point across intelligibly and doesn't resort to relatively uncommon words to do so. Granted, there is a fine line between sounding intelligent and sounding pretentious, and skirting that line is the challenge faced by many beginning writers and even a few more tenured ones. And you don't have to avoid using contractions or beginning sentences with conjunctions—both of which I just did—as if they will make your writing appear too casual, because, in fact, some of the best authors strive to make their literature read very conversationally. Word Repetition This is a more tangible error that may not always be caught while initially writing the first draft. An example: "When you take into account Gengar's great movepool, Special Attack and Speed you realize what a great special threat it can be." No reason to use "great" here twice—swap the latter with "formidable", "fantastic", etc. The word repetition phenomenon can also apply across separate sentences in a paragraph, or from paragraph to paragraph depending on the word. You will usually have to reread your writeup after the fact to catch such repetitions, but a good writer rereads his or her work from start to finish to look for flow issues anyway. Grammatical and Punctuational Errors These are usually the easiest to find upon a second look-through, but still occur commonly enough to make a note about them worthwhile. Strangely enough, the error found most in our analyses contained both at the same time: its vs. it's. "Its" is possessive, and "it's" is a contraction of "it is". An example: "Heracross makes great use of it's Choice Band thanks to two 120 Base Power STABbed attacks." It should obviously read "its" here, not "it's". The reason this error occurs so frequently, in my opinion, is that it's what I like to call a "phonetic typographical error". Our minds say the word "its", but because it is a homophone of "it's", and we use that word much more often than "its" in actual spoken language, we tend to actually write "it's" for an understandably phonetic reason (assuming you were indeed paying attention to the difference between the two when you learned about them in grade school). The same goes for the usage of "than" and "then"—you know the difference between the two, but your "mind's tongue" sometimes says the wrong one. A quick double check will fix a mixup of "than" and "then" if you don't catch it immediately after typing one. Another common error is writing "STAB'ed" instead of "STABbed" or "OHKO's" instead of "OHKOs" (if you choose to not treat both strictly as the acronyms STAB and OHKO). Apostrophes serve two purposes—to denote possession or to denote an omission of one or more letters, as in a contraction. Neither is the case in the above examples, so neither require an apostrophe. Issues involving grammar and punctuation are usually almost as easy to sniff out as are conventional typographical errors and misspellings, though, and can likely all be addressed after a single rereading. Personality One of the more difficult goals to accomplish in writing is to infuse your writing with a certain sense of personality without appearing biased. You don't want to write the entire document in the first person, but you also don't want to write as if you have no passion about the subject on which you are writing either. An example: "I think Floatzel is one of the most fearsome BL pokemon there is, and in my opinion, can work on any standard team with some decent support." In this case, you don't need the first person to prove your point—your writing would be more persuasive and genuine without it here. Observe: "Floatzel is one of the most fearsome BL pokemon there is, and can work on any standard team with decent support." I clearly just removed the "I think" and the "in my opinion", but you can see how much more effective the revised sentence is. Generally you do not want to employ either of those uses of the first person in your writing, because it is implied that the writer feels the way he or she does about what he or she wrote. There are times where a little personality can go a long way towards sprucing up a document. Humor and wit are great ways to showcase personality and make your document enjoyable to read. You are going to want to pick your spots and not overdo it, but if you can find a good spot or two in a paragraph you can go ahead and insert some wit or humor if you can do it without detracting from the writeup in general. The best way to tell if you've gone a little overboard is by rereading your work after you've written it and can look at every sentence and idea and ask yourself, objectively, if the sentiment conveyed is the most appropriate for the given sentence or idea. ***** Well, those are a few of the major things to look out for when writing and editing an article or analysis. After you read over your or someone else's work, you should be sure that, whatever change you're going to make, the initial integrity of the writeup's flow is kept intact. While this applies more to instances where the writeup is edited by someone other than the original author, it is a good idea to recall your own flow and style when making edits to your own document. The best way to do this is by rereading the document until you are certain of its flow and can therefore make edits that observe it no matter what.