General - Make type syntax in header more consitent

[Timi007]

When merged this pull request will:

• Make type syntax in header more consitent
• Make all types UPPERCASE
• Append lowercase s for plural of type
• Use or for multiple options
• Unify types (e.g., BOOLEAN -> BOOL, POSITION -> ARRAY)
• Unify optional argument syntax
• Fix some spelling
• Replace <OPTIONAL> with (default: ...)

IMPORTANT

• If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
• Development Guidelines are read, understood and applied.
• Title of this PR uses our standard template Component - Add|Fix|Improve|Change|Make|Remove {changes}.

Discussion

Nested types

Currently, there are two syntax versions of how the types inside an array are represented:

1. ARRAY<NUMBER>, ARRAY<ARRAY<OBJECT, NUMBER>>
2. ARRAY of ARRAYs of OBJECTs and NUMBERs
   Which syntax should be used?

Enclosure

Furthermore, should each type be enclosed in their own <TYPE> when multiple types are an options?

1. <CODE or STRING>
2. <CODE> or <STRING>

Plural

Should types be pluralized? If so, how?

1. No plural: <ARRAY of NUMBER>
2. Plural, lowercase s: <ARRAY of NUMBERs>
3. Plural, uppercase S: <ARRAY of NUMBERS>

[Andx667]

My thoughts on the discussion:

Nested types
ARRAY<NUMBER>, ARRAY<ARRAY<OBJECT, NUMBER>> seems precise and unambiguous to me.

Enclosure
<CODE> or <STRING> is my favorite here. It's consistent with the other types because its always <type> not < something or something>

Plural
I'm kinda torn on this. Keeping with the consistency argument from before I would choose no plural. But I feel that the added s make it's a lot more clear what is meant.

No plural: <ARRAY of NUMBER>

Plural, uppercase S: <ARRAY of NUMBERS>