Thanks for the patch. I'm still catching up from the Sprint in Prague...

Some comments:
1) User roles and permissions are explained in detail as an item under issues. Therefore it can be shorter in the About section, and we can get rid of the bracktes that way. May something like as short as
"It also allows users with appropriate permissions to manage user roles and permissions."

3) "Creating users": Maybe instead of saying "If allowed" - add a link to the Account settings page, and phrase it something like:If the registration settings on the <link>Account settings page</link> allow vistors to create their own account, then ...

4) User roles: There are now is "administrator" as a third role. How about: "Typically there are three pre-defined roles". Explaining them, and then just explain how to add new roles, and that you then can grant additional permissions.
The roles page is not actually in the admin menu, so maybe we need to say that this is part of the People page?

5) Maybe split user roles and permissions, because that's getting a bit long? It needs mentioning that any new role automatically has all the permissions of the authenticated user.

6) Account settings: Maybe the whole issue of Email texts should be moved to a seperate item? The emails are not only for the registration, but also for requesting new passwords, or when an account gets blocked or deleted. Plus the use of the variables in the text might need mentioning.

I didnt split up the Account settings section as suggested in 6) of #7

I added a section about managing User fields , as this was missing.
It is a bit experimental as this is the first entity type that mentions this option (?)
So please review in such way that it can be re-used in hook_helps for taxonomy, custom block etc

e) Punctuation:
"By adding fields for e.g., a picture, a biography or address you can a create a custom profile for the users of the website."
should be
"By adding fields for e.g., a picture, a biography, or address, you can a create a custom profile for the users of the website."

f) I think a better heading for "Managing user profile" would be "Managing user fields". I think the text there is pretty good, but it should probably say that user accounts are "an entity type" rather than being plural "entity types". The other modules that allow fields, such as Node, just link to the field module and don't say much, but it's a lot more complicated there because the fields are on individual content types.

I think this is great! We probably need someone to manually test it:
- Make sure all the links work
- Make sure the formatting is OK
- Verify that wherever specific pages, buttons, tab titles, etc. are mentioned, they match what you would see in the user interface.