Not sure if my UML USE-CASE diagram is correct?

I would split that Usecase called Register/Login into two separate Usecases. I think these steps are two separate actions and need different steps to execute. This way you are also able to transform the Usecases to Composites.

As you know, a use case is a textual representation of a flow between a user and the system. The use case should have a name that reflects that flow. When I look at your use case names I can see that you have understood this.

The names are all descriptive and well thought through. Well done!

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.