Thanks for the report, looks like a bug in our responsive breakpoints. I’ll make a note to get a fix out for this.
