Before __cursor_search_neighboring was created it existed as additional logic within __wt_btcur_search_near. It also had a comment which has since been modified to suit the new neighboring function. The new comment misses a bit of the previous detail and the original comments should be returned to the code.

The comment should be placed above the call to __wt_btcur_next_prefix and say the following:

		/*
		 * We didn't find an exact match: try after the search key,
		 * then before.  We have to loop here because at low isolation
		 * levels, new records could appear as we are stepping through
		 * the tree.
		 */