Most of the reviewers/answerers here should be familiar enough with Ctrl+K and Home,Shift+▼,Del keystroke combinations that an edit to provide some readability without losing the original content of the code submitted should supercede the site policy of not modifying the OP's original code.
Cleaning up code without modifying the original working functionality should not be considered against site policy per se. In my limited experience, an OP rarely knows the editor as well as someone looking to answer their question. If the intent is to post working code, why aren't commented code lines removed by the editor submission process auto-magically? Kinda like a spam or F-Filter.
Isn't that what the reputation/privileges relationship is all about? I was led to believe that a higher rep meant that the Powers-That-Be trusted that you knew what you were doing and are acting in the best interest of the site. I typically copy and paste the code into its appropriate VS editor. It is only then that I start to actually see the code for what it is intended to do. If I have to make multiple revisions to remove comments and indent to some level of standardization, why shouldn't I edit the OQ and save others the same trouble? If my revisions are ever in doubt the SE system allows for a backtrack to a previous version.
Questions submitted with code lines commented out without complete redress within the question's narrative should never have been submitted in the first place. Code Review should not be reduced to 'throw
sh·crap·it mud at a wall to see what sticks. Genuine submissions should be 'This is what I've come up with. Can you suggest where it might be better?'
I am not trying to do a cut-and-run here. I'm trying to reduce the time it takes me to understand a module's sub procedure(s) to the point that I can see it from a wide standpoint and make intelligent decisions as to how to improve the code.
FWIW, I've been trying to take at least one question and seriously delve into it each weekend since I've been a member. My goal is to find out what the user is trying to accomplish and give them the best that I can offer. To date I have encountered nothing but frustration towards that goal. Today was no different.
¹ Within relevant tags, supplying a dozen or so redacted rows of sample data together with expected results should be virtually mandatory. Visualizing the start to end procedure and end-product from the code alone is rarely the most expedient method. A link to a larger set would be even better but images of data and/or code should be vehemently derided.