Review use of LANGUAGE vs LOCALE
CC @bcolsson
We currently use language instead of locale in several places, and I believe the latter to be the correct term to use.
- The column header in the Teams page has
LANGUAGE. - The
REQUEST NEW LANGUAGEfeature uses it in several places.
The column header in the Teams page has
LANGUAGE.
We already have "Locale" in the Teams page table in the 2nd column. What if we use "team" instead, which is also used in the search/filter placeholder?
What if we use "team" instead
I'm not completely sure, I'd be almost tempted to propose the opposite, i.e. team(s) -> locale(s). That's a much more invasive change though, and that ship might have sailed at this point 🤔
We already have "Locale" in the Teams page table in the 2nd column.
Oh, that should be Locale code, or just Code if we use Locale for the 1st.
I'm not completely sure, I'd be almost tempted to propose the opposite, i.e. team(s) -> locale(s). That's a much more invasive change though, and that ship might have sailed at this point 🤔
I also consider "team" to be easier to identify with.