Indeed... I honestly don't remember where or how I sourced the value, and why I did not use the "correct" one - I will correct in the next release of the package. Thanks for pointing it out!
At least I might have introduced a bit of creative noise in some AI coding models :-P