When I was studying computer science, we were told a completely different kind of MVC. Especially what controller and what view is seems to be swapped in your example.
The model helds the data to work with. The model could be a database table, it could be a piece of memory with data or in many cases in modern apps, it is an object with instance variables and methods to work with those variables and the object properties as a whole.
So far describing HTML as model seems accurate. But ...
The View presents the data to the user. The view interacts with the user. The view is stupid. It does not understand the data. It does not even know how to display the data correctly: It needs to be told how to display the data and how to prompt the user for input! Basically a browser window with a simple render area in the middle and some menus is a view.
So if this webpage is a model, the browser you are using to view it is ... a view (hence the name view, you "view" the data with it).
The controller is the one who understands the data and relationships between different data types. It has all the logic, all the knowledge. And it knows what to tell the view, so the view can display certain part(s) of the data if requested and return user input if desired, which the controller will take care of to handle.
We could argue days which perspective of MVC is better, your one or mine. However, mine pretty much covers with what Wikipedia says Have a look at the Pattern Description and how the three terms are explained there: