Thanks for pointing that out, we've fixed it.