Fix pattern-matching example to use "1" on left-hand side

[catamorphism]

If I'm following this example correctly, the left-hand side of the rule here needs to be 1, not one, since the JS code passes an object whose count property is "1". If I'm understanding MF2 pattern-matching semantics correctly, the comparison between a selector (or rather, the result of evaluating the selector) and an nmtoken key is just a string comparison. So the MF2 code here would evaluate to "You have 1 new notifications", not "You have one new notification", which in turn doesn't match the comment in the JS code.

[eemeli]

This change makes sense, but not for the reason you propose. The numerical value 1 will in fact match a key one, as numbers are compared not only according to exact match, but also according to the number's plural category in the current locale; English uses one and other.

Now, the reason why this change still makes sense is that the content of the message is specific to the exact value, rather than the category. In English, those are the same, but in many other locales, one may be applied to other values as well, such as 11 or 21. English ordinal plurals, for instance, use one for 21, 31, etc. And in this case, the example message refers to one new notification rather than {$count} new notification.