I'm writing documentation. It's technical documentation and my audience should be tech-savvy.
However, I have reservations about referring to UI elements in an interface by the terminology that developers will know and use day to day.
E.g. a dialog may contain a number of combo boxes, radio buttons, and check boxes. But different people may use drop-down lists, option buttons and tick boxes.
The distinction between an editable combo box and a non editable drop down list is not one that I want to matter in the documentation.
Yes, the docs are for the tech savvy but that doesn't mean I don't want to make the copy as digestible as possible for all readers.
So for example:
...change where you edit code by choosing the editor in the [drop-down list / combo box / menu thingy]
...switch on the [feature] by [selecting / ticking / checking / enabling] the [checkbox, tick box, option thingy]
My instinct is to vary different phraseology to avoid needing to reference the name of the controls in this way at all:
...adjust the [some label] option to change the editor used to view source code
...tick the [some label] option to...
.. (de)select [name] and you're done.
What other options are open to me, to make reading documentation better and more enjoyable for my users when referencing ui controls?