If you make detailed comments the whole way through, you run the risk of encouraging the writer to submit sloppy first drafts. Unless it's your job to be the writer's servant, think carefully before taking on that role.
Way in the past I remember the absolute most deadly feelings I got when an actual editor for the first time jumped and killed half of my text before I had done any of my own edits on some website copy.
Writing is highly personal, and others, especially in a basic email, might consider you just excessively nitpicky while focusing on all but the relevant stuff at hand.
The worst thing that the person gets when writing wrong or excessively or whatever is that they will be misunderstood. Eventually it will come back to them in one way or another and they’ll improve and it’s their problem. If someone asks or you ask nicely on the other hand, that’s the way to go, is respectful, friendly and appropriate. Just be careful that they don’t start to keep coming to you with grammar checks :-D
I'm less worried about tickets; they're read much less often, and need to be quickly written without lots of thought.
What is the return on investment, so to speak, in business terms, of getting your colleagues to fix their grammar in internal systems? If they take the time to do so, will business goals be better achieved? Will it bring the company more revenue? Probably not. It might satisfy your perfectionist tendencies but it is not your colleagues' job to do that.
Ticket comments are ephemeral, so let it go.
It's nice and makes it their decision.