Labeling

The word taxonomy sounded "abstract" (exact words) to people, especially if they went to the Taxonomy overview page.

When you get on admin/content/node you get the message "There are no posts available" while "posts" doesn't actually mean anything on this page.

Users are not sure about what "Commonly Used Modules" means when selecting an install profile. At the same time, users think that common modules sound good and use it anyway.

Participant found the description for page to be unclear. Was unable to discern difference between page and article.

Participant had difficulty understanding the concept behind "read only" commenting

When viewing the list of roles at admin/user/roles the first link is the "edit role" link which is rarely needed. The most common "editing" of a role is to edit the permissions. Users tend to click the first link which does not take them to the expected location, to actually edit the permissions for the role, not the role name.

Users find it difficult to configure settings for individual filters. On admin/settings/filter/x, users expect to be able to configure the list of Filtered HTML tags.

On admin/settings/filter, the link is named "configure", but takes you to the "Edit" screen for the format. The user then must click "Configure" to actually change the settings for each individual filter.

Users expect content permissions to be listed under under a heading with "content" and not "node." The interface for setting up content is "content type" with no indication that this is a "node."

On install, the user initially selected SQLite because "MySQL would be overkill for this site".

Once that decision is made there's no going back, and there's no help text explaining the difference.