What is the best way to scan for hallucinations in technical documentation?

So a new team members seem to have spotted some loopholes as well as totally random additions in the documentation. I understood very late that it was a bad idea to run the documentation across 3 different platforms as well. Any suggestions or tips on how to systematically combine the documentation and root out the totally new things born out of the blue over 2 months of documentation. I am not looking for detailed advice just some tips. I would prefer to have some solution before hiring neurotypical person to audit the documentation.

Please take note that this is a product for neurodivergent and the team itself is comprised of young neurodivergent, so yeah.