Should you mention garbled MLS comments and property descriptions on flyers? Should you alert agents to their spelling, grammar, and word usage errors in blog posts and comments?
As everyone knows, grammar errors, misspelled words, typos and garbled sentences found in MLS descriptions are all too common. Before she got too busy to write her weekly post, Gwen Banta entertained us every Friday with MLS bloopers.
And as most know - garbled communication is no communication at all.
The bloopers were funny – but sad for the agents who posted them, not to mention the clients who were counting on them to sell their homes.
This morning, Mary Hutchison left a comment about this on my most recent grammar post in which she mentioned that errors are all too common, especially in MLS descriptions and comments.
My reply to her was that some people don’t know that they don’t know – but surely there’s someone who likes them well enough to tell them they need help.
What about that? What should you do when you see someone consistently making errors that destroy their messages and make them look bad?
When I see an error in a post written by someone who doesn’t generally make mistakes, I write them a private note to alert them so they can go make a quick correction. Thankfully, some Active Rain members do the same for me.
I wouldn’t even consider pointing out an error via the comment function, by the way. I've seen it done, but think that’s a bit rude.
But those are people who know better and just have a typo or a glitch of some kind.
What about the people who appear to "Not know that they don't know?"
When it comes to people who make the same mistakes over and over, such as confusing words like there and their or advice and advise, I don’t.
Perhaps I should. Perhaps YOU should.
How well do you need to know someone before you feel comfortable pointing out these errors? Or how well do you need to know them before they won’t simply resent your interference?
What do you do? And why?
Image courtesy of Stuart Miles@freedigitalphotos.net
Comments (21)Subscribe to CommentsComment