Thanks for pointing it out. This is a known bug that showed up in the deployment to gh-pages. We are currently looking into it.