As one of the reviewers who rejected your edit, let me give some context to the rejection - reviewers don't see comments under answer suggested edits unless they open the answer itself & look. Since I didn't open the answer (usually due to having 2-3 queues open at once) I was missing valuable context - like the implementation of their soql query in the answer was different than the comment suggesting it.
Your edit comment should have stated something like "WHERE cannot be used with Aggregate queries, must use HAVING instead" - instead of "changing soql syntax" - state that the syntax is broken and will not run.
Looking at the answer - leaving a comment under @javanoobs suggestion (which was incorrectly implemented when added to the answer), something like "@RatanPaul you added code incorrectly - should use
HAVING instead of
WHERE, I've suggested an edit", this comment would notify the answerer - who can approve your edit without going through a queue, as well as add context to reviewers who took the time to check the comments.
As for reviewers, we're not perfect, we do make mistakes - and I'd say this is one. What I saw was a user changing syntax, with low rep and without a good reason - thats going to be a rejection. What I should have seen was a user fixing a problem in another users post, who's been nothing but an asset to this community (top 3% this month is no joke).
Once you get to 2k rep you won't have to worry about review queues. If you have another problem like this before then, come to meta - its pretty quiet here & everyone who posts here is very helpful.