Hello, everyone. This should now be fixed. Of course, if you do see it again, please do let us know immediately (if you could tell us what device you are on and the url of the page it's happening on, that would be really useful) but hopefully it's sorted now.