What is the best way to design a database, MySQL?

Question

MySQL

There is a database and I'm not sure if I designed it well. Therefore, I ask for advice on what can be done, how it will be better, criticism of my decisions.
This database must be based on MySQL and used in an application based on the Entity framework C#.
The essence of the application is working with articles, one or more authors can work on an article. The article can be rated like and disliked, and the option to leave comments is also available, which can also be rated. There is a system of complaints that can be sent to an article, comment, user.
Of the current disadvantages that I noticed is that it should be translated into English the name of the fields and tables.
The model was created using ERwin Data Modeler.

Answer 1

Names are a nightmare, not even with the Russian case, that's why you have like / dislike in one place it's 'status', and in another it's 'like'?
Add everywhere (articles comments likes complaints...) creation time/last edit time needed for output order
Likes and complaints need a link to the user who left it, will almost certainly need this information later.
Directory category of the complaint is not clear why there are two fields title and description when there is a note in the complaint itself, but these are trifles . It is bad practice
to store the user's password (for example, store its hash, some sha256), but this is already at your discretion, so how to determine the authorization process