I've seen entire codebases riddled with method names that could've been taken straight from the latest sales pitch made up by Marketing. I think it depends on what kinda company you are. The more "sales-driven" (for lack of a better wording) your company is, the more likely you are to end up with words like "human assisted training" to describe a non-AI related configuration process.

I would say techies also get caught up in this behavior sometimes.

We had to change the names of our API function calls when marketing updated our product name :(

Well I have to say that some command/API names on unixes for example are horrible. What's up with killing processes. Can't we just say terminate. Since software is mostly developed by a geeky bunch we sometimes forget that we are actually making something to be presented in an appealing manner to a buyer/licenser.

Which means you used a bad naming convention. I hope you updated them to something that is descriptive enough and yet won't need to be changed next time marketing decides to change the product name.