The idea is usually explained as “use the same words as the business”, which sounds like a style preference. The version with consequences is that a word meaning two things is a boundary the code has not drawn yet.
// the word 'order' means three things in one namespace
class Order { } // sales: a basket that was confirmed
class Order { } // warehouse: a picking instruction
class Order { } // finance: a revenue event
// which is three contexts wearing one name
SalesOrder WarehousePickList BillingInvoiceRenaming to the words each side actually uses is usually resisted because the classes look similar. They are similar and they change for different reasons, which is the definition of a seam. Where the business genuinely has one word for one thing, the code should use it exactly — including its awkward plural and its inconsistent abbreviation.