Tons of openSource (and other) projects have cutesy, catchy names usually derived from some acronym.
That's fine for the project, but useless for the user.
If I'm looking for DNS settings, do I really need to have a degree in openSource trivia to know that Unbound is the place to look for it?
If I want to fix settings in the http proxy, do I really care to know that it's squid I'm using?
You get the idea: it's sometimes obnoxiously difficult to find the things one needs, because packages, services, settings menus, etc. are all named after the project, rather than after what they do.
e.g. PostfixForwarder should be an SMTP Forwarder/Proxy
e.g. Status > OpenVPN should be Status > VPN (OpenVPN) and
Status > IPSec should be Status > VPN (IPSec)
Because things are not named by what they are, but simply after the project, or slightly better after the protocol, and then sorted alphabetically, related things can be at opposite ends of the menu list.
Think about it: if you go to a restaurant, are the food and drinks mixed up and then listed in alphabetical order? Or do you have a category with soups, appetizers, etc. and then maybe sub-categories e.g. beef, chicken, fish, and vegetarian?
It's likely much too late to do this for the 2.0 release, but I think the way things are named and sorted in the menus and package lists should be changed.