There was nothing particularly complicated at work here, just a simple typo, which has since been fixed and should be reflected in the next update. Sorry about the confusion!