He fails just like almost every other OOP explanation out there. The proper way is to, once your audience knows C, explain how OOP can make programming more simple and efficient by replacing structs and pointers to functions with objects containing methods and data. That is better than pointless hand-waving about how OOP can model real-world objects.
tl;dr:
- you have one or more structures containing data
- you have one or more functions that, taking a pointer to said structures, does something with the data
- the structure definitions are the classes
- allocated structures are objects
- the functions are methods of the class