Japanese RPG games does something interesting. When you get a quest like "Go to the house of MrTom and pick the toothnail" the words MrTom and toothnail are bolded. Something in the system (maybe is done manually wen the quest text is written) acknowledge entities in the system ( NPC characters, locations, items) and bold it, so is easier for the player to tell the important parts of the quest without really reading it full trough it.
Computer geeks use to do this using the * character. "fixed wikidata bug by reversing the *polarity*". This type of ascii syntax is what started the wikisyntax.
It could be interesting (but I have no idea if is feasible), if git recognize automatically elements in a commit text, and colorize it on the terminal screen (or maybe bold it if the screen renders using truetype fonts). This way, if you have written wikidata many times, you will quickly spot a problem if the commit renders to you with "fixed wkidata bug by reversing the polarity" and wikidata is not bolded/colored different. A alternate would be for this script/program, to extract keywords and present to you, so if you notice the commit lack the label "wikidata", theres something wrong.
Many times people don't read what are writing, only when are given back what have write notice that theres something wrong in it. Many Internet forums recognize this by allowing people to edit / fix post in the first 5 minutes. Anyway half the battle is making so people care about this,so put a bit of effort into writing without many spell errors. Perhaps is harder if you have people from different cultures, and you have developers that are not english natives.
If people not care, will always make this type of mistakes, and if the mistakes change keywords like wikidata or function names, it may make commits harder to search for keywords. It is true this thing is so minor its not even worth a thread on the mail list. I am posting this here, because is a fun problem.
--- The Swedish Chef