I've had to learn this lesson. We have an internal microservice whose name is obsolete and no longer makes any sense whatsoever. Everyone is confused by the name until the original reasoning is explained, and they come to understand the original purpose of the service, now long since changed. It drives me up the wall.
I have time and time again made a case for renaming it to accurately represent its modern purpose, which would take an engineer about a week of work - there's a lot of code and config that has to be switched over.
The person running my division has shut me down on this over and over. It goes like this:
Manager: Why do you feel this is a priority?
Me: It confuses people and makes the code less self-explanatory.
Manager: How much time is this costing engineers?
Me: Well, about a minute every time I have to explain it to someone once a week.
Manager: And it would take a week to update? This doesn't seem like a good trade.
Me, mentally spluttering: But the name makes no sense!! It's the wrong name!! It's completely unrelated and has no meaning!
Manager: Do you think you can work with it anyway?
Me: sadly sighs.
I think the manager is right, as much as it offends my sensibilities.