This has been fixed.
Thanks for the report.
Sorry about that! We just noticed this today.
It’s been corrected internally.