Q:

According to the Use case <>, can we say that the diagram is correct?

In my project, users (admins and education expert) are able to see dynamic reports. These reports are created in the Report File Manager. 
Now, to draw up a use case view reports, Is the following diagram correct?

It should be noted that the admin are able to view all the reports and the education expert is able to view his self report. Will this change use case diagram?
//////According to the answers,I've drawn a new diagram.

A:

The first thing I notice is your strange actor notation which I never have seen anywhere. An actor is shown as simple stickman.
You will need to add a constraint to describe that the admin can view all reports. This could simply be a textual note in curly brackets like { admin can view all reports} attached to the association between actor and UC.
Besides that, think about collapsing all these single CRUD use cases into a single Manage Report since I guess that all are strongly connected. Else you're likely to be struck by the functional-descomposition-syndrome.

