Wording & Phrases

Try to keep phrases short. Shorter phrases are easier and faster to interpret and give more alternatives for designing the layout.

Avoid complex phrases involving backslashes("/)" and paranteses for the same reasons as above. It also makes translations more accurate.

Use "Monitor" instead of "Display". The main reason is consistency but also because "Monitor" is not a verb (easier to translate and non ambiguous) as well as it more directly refers to a physical Monitor - the word Display has more denotations. A negative side is that people tends to associate with "old" CRT monitors, while there now a days exists exists all kind of fancy stuff like TFT screens. For some users this does not cause a problem. For example, one of the authors of these guidelines are well aware of that such nifty things only exists in his imagination.

Generally speaking, use "Hardware" instead of "Peripherals". Hardware is less technical and not as abstract as Peripherals. Everything classified as Peripherals also classifies as Hardware, and thus the substitution can't be misinforming, although possible vague(but that can also be a good thing). There is strictly speaking cases where Peripherals is more semantically correct but the usability aspect of the choice must be deeply considered.

Avoid including words like "Management" and "Configuration" etc. since it is abundant - KControl is all about that, which the user already is aware of. Furthermore, such terms does not inform the user about what your module contains, except that it is for configuration or management(and that is already clear since it is in KControl).
Another reason is that it makes it more cumbersome for the user to find what he/she wants. For example, if the user looks for monitor settings the word "monitor" is looked for, not "settings". Thus, the phrase "Monitor" can look incomplete and half baked compared to "monitor Settings" but actually fullfills its purpose better than the latter.
Another example, pick "Sony Vaio Laptop" in front of "Sony Vaio Laptop Hardware Configuration" since the user already knows it's about Configuration and Hardware.

*nix systems are built around the multiuser paradigm, where a administrator usually are available. This have changed a lot - KDE is usually installed on regular desktop machines where there is no adminisrtrator and messages like "Your administrator has disallowed ..." is percepted as out of context, awkward and constraining - avoid it if possible. Inform the user where this "lock", permissions or what it is about can be changed. It is very likely the regular user also is the "root" or administrator user. There is of course cases where this can not be avoided.

As above, try to keep in mind how the user sees the computer as opposed to you, the developer. For example, usually there is no bigger distinction between "KDE" and other software components(such as X, kernel), don't categorize and use phrases which builds on a technical understanding on how the computer is built, but rather how the user percepts and orientates.

KControl as the rest of KDE targets a wide audience where a majority(to say the least) of the users does not have technical expertise. In order to have a compelling interface it is important to avoid technical and "scary" terms. The goal is to reach the user and communicate successfully - that is not succeeded by using words the user does not understand or feel uncomfortable with.

The above name recommendations is guidelines and must not be strictly followed. If the name demands to be longer than average in order to be informative that is of course ok. Similarly, don't simplify words in case it then does not reflect the content. The recommendations exist to make the names informative, representative for the content and easy to read - not the opposite. The recommendations can also be applied on phrases used elsewhere in the KCM.