This has now been fixed and will be included in the next released build. Thank you for spotting this.
