I can understand where you are coming from! Each and every time something new comes out, rather than explaining things straight-forward, you get a mix of different explanations as to how to do what you need to do, and a plethora of ways to accomplish it.
That aside ythe business logic in this type of framework typically (though not always as it depends on how your application is architected and designed) goes in the Model. The View is typically what you would use for the presentation - a web page / form for example. The Controller for lack of a better explanation, is like a "coordinator" between two parties (the go-between), taking in requests from the View, passing them through to the Model, getting back a response and sending it back on to the View.
Of course this explanation is not infer that logic of "any kind" would not be part of a Controller class, but in the context where you might be talking about where you might put the business logic for your business class (such a Product class), the Product class would represent the Model and would contain it's business logic.
As well, depending on the design of your application, the logic may further still be placed in yet another class in some other tier in the application and the business class, such as the Product class example I used above may be something as simple as a data transfer object (DTO) and serve as the Model.
Anyway, I hope this helps a little more.