[jc104]

Just posting to say that I agree with the standardising of these things, although I couldn't care less whether there is a hyphen or not. As for the capitalisation of move names, I think it is preferable to use the full name of the move where possible, particulary where what is written has a different meaning outside of pokemon.

As for the issue with the set names: in theory, when a prefix is used in front of a proper noun, a hyphen should be used. This is silly so I'm not suggesting making it Cro-Cune, but it means that whatever we do, we are breaking the rules. This means either way is equally good in terms of pure grammar. However, I believe CroCune to be superior, simply for reasons of clarity for new users.

As for the "you" thing, it should definitely be enforced on occasions like that posted above by Fuzznip. In a sentence like "you can OHKO Gyarados with Thunderbolt," though, I am less sure, since you do select the move to make Jolteon OHKO, and as such you have indirectly OHKOed Gyarados.

Also, I would quite like to mention two words that really annoy me when they are used incorrectly: "utilize" and "abuse". Both of these words are actually fairly similar, in that, particularly in the case of "abuse," they imply the use of something outside of its intended purpose. "Abuse" is more negative and suggests damage. In most cases in which these words are used, the moves are being used exactly as intended, and should as such be changed to "use" by grammar checkers. "Abuse" should be left to very extreme situations - even Jirachi's Iron Head is used as it was designed.

However, these errors have been made so often that it could be considered almost as standard, so I will wait to see what everyone thinks.

There is also one last thing that I feel needs to be clarified. I notice people regularly hyphenating stuff like "Normal-types". Note that this is not being used as an adjective before a noun "Normal-type Pokemon" or "Normal-type attacks." You also have things like "Blissey is a Normal-type." Given that no ambiguity can be created from this, I cannot see why it needs to be hyphenated. (note that I made up the examples)