That should be fixed now after a hard refresh. Thanks for the heads up!