docs: fix typo - count should be model

[EtherNoteWorld]

Description of Problem

When I read the documentation, I am unclear about the source of this count.

Proposed Solution

Additional Information

[netlify]

✅ Deploy Preview for vuejs ready!

Name	Link
🔨 Latest commit	dec7a37
🔍 Latest deploy log	https://app.netlify.com/sites/vuejs/deploys/65f28c4e92686800081033f8
😎 Deploy Preview	https://deploy-preview-2749--vuejs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[brc-dd]

Actually, the name doesn't matter in parent component. It can be count, foo, bar or anything else. This change might be bit confusing for new users as they might think that the variable name should be model too. I'm fine with either one though.

[AloisSeckar]

As an occasional contributor I object against this chage as it goes against clean code principles. Naming the variable model makes sense inside the component itself, because there it has clear purpose - it "models the actual data value for this component". But from parent's perspective you want to know, what data you are passing to your child, what they represent. Therefore count makes sense, if you are displaying, let's say amount items in shoping cart, but model is nothing. If you use two child components, will you name your variables model1 and model2? How about having ten children?

But maybe we should make clearer, why count is used. I will think about some wording, if noone else does.

[bencodezen]

Agreed with @AloisSeckar. I'll propose some changes in the PR to accommodate the general momentum we seem to be heading on.

[bencodezen]

Naming the model model can lead to future confusion. Suggesting changes shortly.