This isn't about enforcing how new things are named, this about enforcing using already existing names consistently. If the documentation says "there is a thin

This isn't about enforcing how new things are named, this about enforcing using already existing names consistently. If the documentation says "there is a thing named foobar", but in the code I can see Foobar, FooBar, FOOBAR, FOObar, etc. used interchangeably, that's not gonna help readbility and maintainability.