The discussion revolves around customizing site text in Discourse, focusing on the pros and cons of altering UX copy. Suhotra_Roychoudhury raises concerns about the extensive list of text areas that can be modified and whether changing default text might disrupt uniformity or complicate instructions. Jagster notes that customization is common since default text is a compromise for all users, and consistency in terminology is key. Simon advises that changes should only be made when there’s a clear reason, and recommends using ‘verbose localization’ to identify where text appears in the UI. pfaffman suggests considering language translations as an alternative. Suhotra_Roychoudhury confirms the intention is to edit UI/UX text using the Admin site text option.
It is totally up to you, and a little bit how users see it. But of course it is smart to keep some consistency and use the same word or expression in the same context all the time. But that depends. English, and the English used in more IT environments, is actually quite limited or poor, there isn’t too much variety.
But customization is quite a common thing to do, because defaults try to be ones that suit everyone, and are then a compromise.
Only do it if you have a reason to make the change. There are cases where there are good reasons to customize the text.
Have a look at this topic: Find a translation key with verbose localization. It shows you how to enable “verbose localization” so that you can see exactly where in the UI the text for a translation key is used.
If you enable verbose localization, use the method outlined in the “Enabling the setting for an individual session” section of the guide (Find a translation key with verbose localization). Enabling verbose localization through the verbose localization site setting will just make the site look strange for its other users.