Question about data types specified in the API documentation

[VirtualVirgin]

I'm noticing that there are differences in the capitalization for some data types in the API docs,
for example:

Content.addAudioWaveform(String audioWaveformName, int x, int y)

There is "String" and there is "int".
Is there something I can learn about this distinction?
I am assuming there is a reason for the different treatment given the consistency of usage:
"Array", "Object", "String"
vs
"int", "var", "bool", "double"

[d.healey]

@VirtualVirgin

If the mixing of uppercase and CamelCase triggers your OCD, rest assured that this is not a case of me being sloppy but trying to use the existing type IDs from Java/Typescript (eg number ) but for the complex types like Array and Buffer I have to stick to the existing HiseScript identifiers.

https://docs.hise.audio/scripting/scripting-in-hise/additions-in-hise.html#type-safety

[VirtualVirgin]

@d-healey Thank you!
Though I am still slightly confused on the use of "string" instead of "String" in the list of accepted types (given that the API reference uses "String"):
string elementary a string variable

[d.healey]

@VirtualVirgin I think both work, not sure