I think it's a bit clearer to write "page queue".

Whether or not a page may be paged out is really up to its pager. In practice a page not belonging to a queue will not be paged out, but it doesn't have to be that way.

More specifically, pages in the active queue are (probably) mapped into some address space.

You might note that the page daemon periodically visits active pages in order to decide whether they have been recently accessed.

This is a bit imprecise: "referenced via a page table mapping" is more correct. Unmapped pages may be recently referenced (e.g., by sendfile) but still end up in the inactive queue.

A page itself is dirty, not its contents. It may be helpful to explain what "dirty" means, or reference some documentation which already does so.

This only happens when the system is under memory pressure. The laundry thread does not free cleaned pages, it moves them to the (head of the) inactive queue for reclamation.

Typically we use this when swap is full or no swap devices are configured.

What does "touched" mean? In general, most kernel code does not need to know about page queues at all.

"Each .Xr numa 4 domain in the system has its own set of page queues."