Properties are half way between methods and variables. Unity and Unity developers have a habit of treating them more like variables. .NET and .NET developers tend to treat them more like methods.
Unity land is generally less strict on pure encapsulation principles then .NET land. This is because Unity’s serialisation system does not play very well with properties and encapsulated data. As a side effect of this it often makes sense to retractor a variable to a property, or vice versa. Having the names identical means you don’t have to change the public API.
On the other hand .NET land encourages strict encapsulation. To the point where there are no public variables, everything is accessed through a property. Thus there is never any need to change the public API.
You’re using unityscript, and there’s no real naming standards defined for it.
You could apply the C# standards to it, which is what that article covers.
If you want to understand the standards laid out throughout the unity API… that was covered by @Kiwasi . Unity doesn’t capitalize it’s properties, and instead follows a more ‘javascript’ standard (javascript does have a standard, unityscript does not), for the reasons BoredMormon stated.