Thanks for pointing that out. We've fixed it now.