Thanks, Nick, and great catch on spotting the oversight. I corrected this last night, and a new update is now available.
