The field of Automated Program Repair (APR) has seen significant growth in the past decade. As the field progressed, the template space in which patches are sought after has grown substantially, to increase the number of patches included within the domain each tool finds fixable and, thus, increase their fixing capability. However, this heightened potential was not free: new techniques paid by using greater computational resources and time to look over an enlarged repair space. In this paper, we look to curtail this trend by using language models (LMs) to provide guidance about whether a generated patch is natural. By prioritizing patches that generate natural code, which has been demonstrated in prior work to be related to correctness, we can reduce the number of patches that must be inspected to find the first correct patch. We evaluate this prioritization scheme over five APR tools, and find that we can reduce the number of patches that must be inspected in up to 70% of bugs and reduce the total number of patches inspected by up to two-thirds, paving the way for lower-cost program repair.