Thanks for pointing this out, we have fixed the error.