How so? The page looks like HTML5 to me. If the title were "Device Mockups Using Only HTML5," then your point would be slightly more valid, although it has become quite common to use "HTML5" to refer to all client-side technologies in the modern web stack.
I totally agree with this. I used to be pretty picky about how the term HTML5 is applied to new products, snippets, etc., but I've realized that it refers to a very specific context. It's much more efficient and descriptive to associate something with all the modern technologies we're using on client-side by tagging it HTML5. If we call something "modern", it is doomed to be slightly ambiguous and always shifting -- people called some technologies modern back in the '50s; are they modern now?
Even though calling something HTML5 may not be semantically appropriate, it's a nice form of metonymy and it instantly orients the audience with the frame of mind the author intended.
Is it really useful to whine about this? A word gets adopted to describe something that would need a sentence, that's fine even if the word has other meanings and gets distorted. It's like AJAX ten years ago when people bitched that you were using JSON instead of XML.