>>>PS: I can't believe even spelling and or grammar errors were recorded as bugs.
>>
>>Obviously you didn't have me for a boss :)... or didn't have anyone like some of my bosses. Though, I didn't count them as bugs, but they had to be fixed anyway.
>
>ROFL. I would call them 'buglet' (just introduced a spelling bug I think:)

Buglet is a word (now :).

Actually, the grammar was more a matter of confidence. As one of the customers told his operators (but probably addressed it to me as well), "an invoice, despite coming out of a computer, still has to be so perfect, with customer's name and address flawless, that the customers likes it so much as to get a desire to pay right away".

People really pay attention to this. I've heard "look at these guys, they're illiterate. I bet they don't know where their head is and where their ass is. We'll pay them much later, they won't know." Or, when demoing something to a professional audience, they'll notice those things and you've gone down several notches in their eyes.

As for the text an application displays, perfect grammar comes second, after clarity. Any ambiguous text sooner or later ends up with user doing something you didn't intend. I'd count that, if not as a bug or buglet, but then at least as a design flaw. For instance, any messagebox() where you have to press "No" to actually do something falls into that category.