In order to account for different regions having different terms for the same thing, certain terms/concepts are referenced via some common NLS so they can be easily replaced everywhere in the system and do not have to be laboriously replaced everywhere they appear.

Common terms are defined in an NLS file just like other strings, and can be overridden as shown above, under the 'common' path. These common strings are referenced in the NLS as embedded variables using the same format as other NLS substitutions, for example:

 

Unlike other NLS strings, the key of the common term can be capitalized to capitalize the end result, for example, 'Edit {common.Event}' will become 'Edit Event'. This avoids having duplicates of all the capitalization options in the common NLS.

An example of overriding common NLS terms can be found in exampleCustomConfig.jsonc:

There are some issues around grammar when doing this, so, in addition to event, in the common terms above we also have a_event, defined as "an event". This is because if we wanted to call events jobs, we couldn't just replace event with job, as "an job" is not grammatically correct. Having an event defined as "an event" allows it to be changed to "a job" and so the substitution works grammatically.

Similarly, we have openSwitch and openedSwitch, to account for the instruction versus the state.