The documentation of the behaviour of 'threads=auto' in containers is incorrect

The documentation claims that threads=auto would cause MaxScale, when running in a container, to use the CPU resources available in the container when deciding how many routing threads to use. That is incorrect, MaxScale will always base that decision on the number of cores available on the computer in which the container is running. That may lead MaxScale to use more resources than what is available in the container.