Thanks for bringing this to my attention, I think it was a caching issue. Seems like it’s fixed now.