Yes, you’re right! Thanks for pointing this out. I checked and this bug has been fixed in the interim, so it’s correct now.
