the way QueryFactory and Query work with namespaces and classes needs to be documented

There is some documentation in \Drupal\Core\Entity\Query\Sql\pgsql\QueryFactory:

 * To add a new query implementation extending the default SQL one, add
 * a service definition like pgsql.entity.query.sql and a factory class like
 * this. The system will automatically find the relevant Query, QueryAggregate,
 * Condition, ConditionAggregate, Tables classes in this namespace, in the
 * namespace of the parent class and so on. So after creating an empty query
 * factory class like this, it is possible to just drop in a class extending
 * the base class in this namespace and it will be used automatically but it
 * is optional: if a class is not extended the relevant default is used.
 *
 * @see \Drupal\Core\Entity\Query\QueryBase::getNamespaces()
 * @see \Drupal\Core\Entity\Query\QueryBase::getClass()

but it doesn't explain the implementation details and it's hard to find!

Thanks! Looks good, just needs a few tweaks.

Small changes

Think that reads better.

Committed 0b7d095 and pushed to 10.1.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.