max-read-page-bytes and max-read-page-message are already in doc but they need to updated as a result of the addition of the prefetch parameters described below also (All updates are in asciidoc file attached

 
max-read-page-bytesMaximum memory, in bytes, that can be used to read paged messages into memory per-queue. When applying this limit, the broker counts both messages messages in memory that are ready to be delivered to consumers and messages that are currently delivering, that is, messages pending acknowledgement. The default value is 20MB. If consumers are slow to acknowledge messages, you can increase the default value to ensure that the allocated memory is not consumed by delivering messages, which can starve the broker of messages.
max-read-page-message
Maximum number of paged messages that the broker can read into memory per-queue. The default value is -1, which means that no limit applies.

prefetch-page-bytesMemory, in bytes, that is available to read paged messages into memory per-queue. When applying this limit, the broker counts messages messages in memory that are ready to be delivered to consumers but not messages that are currently delivering. The default value is the same as the max-read-page-messages default, which is 20MB. The default value is optimal for an environment where consumers acknowledge messages quickly, so the allocated memory is not consumed by delivering messages.
Note. If the value of the max-read-page-bytes is reached before the value of the prefetch-page-bytes, the broker stops reading further paged messages into memory.
prefetch-page-messagesNumber of paged messages that the broker can read from disk into memory per-queue. The default value is -1, which means that no limit applies.
Note. If you configure both the prefetch-page-bytes and prefetch-page-messages attributes, the first value reached applies.