In the beginning (at Ask Ubuntu), I made many edits with this kind of summary. I thought That was OK, since there are reviewers, who actually see my edits, and I also think that was good suggestions. ( 1/66 is rejected, for the rejected one, I also feared that might be rejected ).

But now, I see that, this kind of summary may confuse reviewer or create annoyance. So, I am now changing that habit.

But to me, I think the last option sounds best. Since those summaries are hidden. (Not because, I was doing that....)

In the beginning (at Ask Ubuntu), I made many edits with this kind of summary. I thought That was OK, since there are reviewers, who actually see my edits, and I also think that was good suggestions. ( 1/66 is rejected, for the rejected one, I also feared that might be rejected ).

But now, I see that, this kind of summary may confuse reviewer or create annoyance. So, I am now changing that habit.

My answer will be (After knowing that the edits are not hidden) : Option 5, that is post a feature request, asking users to remind about good summaries by adding something with this one:

We welcome all constructive edits, but please make them substantial. Avoid trivial, tiny one-letter edits unless absolutely necessary.

Because, that helped me to avoid unnecessary edits, might also help me (and many others) to avoid typical, two worded summaries.

Also, if a certain pattern is found on the summary string, we can warn user with a warning like this :

Finally, We need to remove these strings as suggested summaries: (Because that does something for my short edit summary habit )