Hey @Fixi and @Narelle
Thanks for spotting this. We’ve relayed it to the team so it can be fixed in a future revision.