Review with questions, not commands

I think a fundamental problem with your review process is your idea that you need to force anything down their throats. Instead, ask questions like "Why did you decide to go with X approach instead of Y?"

This will make them think about their own coding process, instead of forcing them to accept your coding process. And hey, you might learn something too.