If you are reviewing pull requests to your code base, what aspects do you focus?
I am asking, because a colleague of mine most of the time complains about minor code style issues, like the following:

"why is that method static, it belongs to the object. I am not used to static methods, please adjust"

"the methods are not arranged in a standardized breadth-first order"

"Please use that other kind of initialization..."

Those nit-picks make me crazy sometimes. Is it just me?
I mean, her reviews also contain valuable content, but those small complains about coding style feel like "I did not found anything else but I have to". ^^

Me being confronted with multi dimensional data in CSV files...

I only write documentation, so that I can tell others to ReadTheFuckingManual some day!
:)

Damn, I hate it if asking a question leads the counterpart to telling long background stories. Please: Just. Answer. The. Question.

I have my own thoughts and reasons why I ask and don't need your interpretation of my question. If I was not specific enough, please ask back.