There are a couple of examples of this. It makes it difficult for users learning the system and inhibits training. This has been an issue for several years now and is agreed by all customers I have spoken to as a blocker to understanding and using this functionality.
1 - When creating a PM Plan template and adding a schedule the lookup field to 'Task Template' is named 'work order purpose'. This should be named with the object name.
2- Available Service. The object is called 'Available Services' but in a number of places it is referred to as 'Service". Example if you when looking at a view of all available services hit the 'new available service' button then the next screen is titled 'Create Service' instead of "Create Available Service'. Another example is when adding to a 'Service Plan' a 'pricing rule',
3 - 'Service Plan' object, this is essentially a template to be used to create contracts for customers. It would be logical for it to have template in the name. 'Service/Maintenance Template' for example.
4 - When adding 'labor pricing' to a 'service plan' there is an 'activity' field to populate which looks to be referring to the 'activity type' instead.
5- When adding a service offering to a service plan there is on each row added a field called 'Service Type', this is actually a lookup to 'Available Services' so it should be named as per the object.