I think "too localized" would be appropriate in such a case... A simple proof-read of the code by the OP would have prevented the issue - point it out to them and VTC.
It is possible however that this one small spelling mistake is not the only problem with the code - one should also consider the same code without the mistake and try to see if a problem still exists. Sometimes the error could have been caused by the OP rushing to post the question.
The only reason I can see for leaving a post like that open is that other people can see how embarrassed the OP was and they'll make an effort to proof-read their own code before posting :)
An important thing to note is that these posts should not be edited to fix the typo!
Yes, spelling mistakes and tiny syntax errors are frequently closed as too localized. Usually, the people who posted answers will not vote-to-close out of fear of losing the reputation they gained. I almost always need to flag these for moderators because no one else votes for them. I think the general majority just don't look hard enough to see when questions are too localized or not.
There is one instance where they should not be closed - if they are exceptionally well documented, including the specific error that the typo gave them. Others will have similar problems in the future, look up the error issued, and have one more thing to check when nothing else helps because they'll keep overlooking the spelling issue.
I don't believe we need a community policy to close such questions, mostly because some users will close them blindly without taking into account that some of them will still be worthwhile.