The Declarative State Machine Framework documentation says that State inherits after QAbstractState, while it really extends QState

Documentation says that State inherits after QAbstractState, but when looking at source code I've found that it inherits after QState. Is there any reason to hide the fact that State is a QState subclass?

It matters when you want to create a C++ class with state properties accessible from QML. Class QState has some interesting functions that could be useful in C++ code (but maybe also problematic), so I wonder if they were deliberately "disabled" this way or if it's just a mistake in the documentation?