Still there are missing the descriptions of relationships. Looking at your model, I don't know what kind of a reletionship is between USER and CONTENT.

Is a user creating a content, reading, rating, requesting a piece of content, etc? It is good idea to have the names of relationships. Like USER has ACCOUNT, USER belongs to GROUP, GROUP is managed by ADMIN, EMPLOYEE works in DEPT.