Good catch! We'll fix it on the next deployment in the next couple of days