Hi, thanks for testing out. That is the original implementation actually. Initially we put h4 there so that the whole document flows once from h1 accordingly.
But after further discussion, we decided to separate the document semantics so that the content area has a different h1 than the page h1. This is to ensure trouble-free transition from the current template too. I do agree that it is semantically meaningless to apply such class to a p tag, but definitely not semantically wrong.
But making the classes more global will definitely help devs in using it in other tags besides from p. I will apply your requested changes to the next commit in the cvs.