If your current approach to get them to get their code better doesn't work, why don't you a step back and see what's wrong with it? Sometimes, the more direct

If your current approach to get them to get their code better doesn't work, why don't you a step back and see what's wrong with it? Sometimes, the more direct and assertive you are to people that tend to get defensive, will make them more defensive. Maybe break down their barrier by making them trust you first? Make them see what they do wrong indirectly first instead of pointing it to them? Maybe try to understand their thought process first and see if you can learn from them? Maybe his intention is sound but he couldn't communicate it clearly to you out of nervousness? Or maybe you can get to the basis of their logic, the root cause, and tweak it from there! Anyway, I am actually curious what do they mean by your PR comments crossing the line? In what way? Is there some mistake made due to cultural differences? Maybe bring the discussion to a more public channel, a common ground, and get help from an expert from a neutral party. But this approach will need you to make sure you don't have the slightest bit of intention to bring them down ad hominem. At least, if you want to change the person, you would want the person to acknowledge first why they need to change.