Good catch. I've fixed it in the original post, and documented the update accordingly.