The guides at Ember.js Guides - Guides and Tutorials - Ember Guides seem to mesh together the terms “content property”, and “model property”. I would have raised a bug - except I’m not so sure. Is this merely a typo? Or could we simply just standard on one term, and just call it that, instead of calling it by 2 different names?
I don’t think it’s really a bug, since in the controller they mean the same thing. But having two different words for the same thing makes it confusing, and doesn’t help with the docs.
I saw @tom comment on an issue on GitHub and say, model == content and that model is the preferred property to use but for backwards compatibility content will be there for the time being.