Some very general terms, with special meaning in commerce need translation contexts.
One more example I just ran into was "Review" checkout flow state.
See in how many projects the term "Review" is used: https://localize.drupal.org/translate/languages/de/translate?project=com...
Commerce's shopping context is too specific to use the general term without translation context.
In German for example "Review" means things like
Someone now translated the general "Review" Term with "zur Freigabe" which would ne "For approval" in English. It's not totally wrong, but definitely unexpected in this context.
In this specific case "Review" could either be changed to "Review order", which would give the combination more context or we could use the t() context array value something like "commerce" or "checkout".
I'm not sure if we should have a meta issue for that or simply solve each case that appears just individually or by context...
But I tend to say we should add context everywhere in commerce where such general words are used to make them distinct from very different use-cases.
Needs review
3.0
Checkout