Should "administer content" allow user to delete any node?

I'm not entirely sure if this is a bug or not. When I grant a user the "Administer content" permission, that user is able to delete any node using the update options on /admin/content, including nodes of content types for which they do not have any delete permissions (or any permissions at all, for that matter). I'm not sure if this is intentional because in the /admin/content view, the user does not see the "delete" link as an option in the Operations column for nodes of that content type, which would suggest that they should not be able to delete those nodes by any means. Similarly, if that user goes directly to /node/[nid]/edit, they get an access denied message (because they don't have edit privileges).

What I'm trying to do is give a content owner permissions to change the published and promoted statuses for some content types, but without giving them the ability to delete any and all nodes site-wide. It seems I can only give them publish/promote control by granting the "Administer content" permission, but as I noted, this seems to grant too much access. The expected behavior, I think, is that by granting "Administer content" permissions, that user can set published and promoted statuses, but is limited to operating on those content types which they have been granted add, edit, and/or delete permissions.

If everything is working as intended, feel free to close this ticket.