Problem description

I understood from #432 that APIs can now decide to allow to pass more than one SubscriptionEventType within a subscription request. But the following line

still states that it MUST be only one, and the use of multiple values will be open only "later" at API level:

Note: An array of types could be passed but as of now only one value MUST passed. Use of multiple value will be open later at API level.

Expected behavior

The current formulation is at least ambiguous and might be better aligned with the template which states "Note: the maximum number of event types per subscription will be decided at API project level".

Alternative solution

Additional context