Thank you for bringing this up! Another user had spotted a similar problem so we'll have this issue fixed by the next update! Still trying to figure everything out on our end so apologies for the confusion.
