Lee Carré (2021-10-12 12:10:40+00:00): “Maxar imagery and Mapbox Satellite help me with this edit
http://www.osm.org/way/989908342”

Then your changeset comment is incomplete / misleading.

What makes for http://wiki.osm.org/wiki/Good_changeset_comments

“I realized that I cannot upload such big edits cause it's hard to validate changesets and contradicts osm wiki recommendations.”

The area is one problem, but another is nature / type of changes and the comment=* .

Besides logical separation of unrelated changes into different sets, this better allows the comment to be scoped more precisely.

One set for changing names of ways, another for adding water features (especially to a different area), and the next set for something else.

Even if they're geographically close; different sets for different changes is a good idea. Think of why StreetComplete separates changes by quest-type.

For example, while surveying if I found a street_cabinet and a fire_hydrant on the same corner, since they're unrelated (except by location, which is only a weak association for those two, and may just be coincidence) I would use a separate set for each. This makes very clear which comment relates to which elements. Plus, keeps discussion of one separate from the other; someone else may be interested in infrastructure but not emergency equipment, or the inverse.

However, if updating the tagging (and maybe position) of retailers along the same street, that might make sense to group into a set (rather than one per retailer), since they're related by type & location, and the same kind of change is being made. However, I would still definitely use different sets per-street, rather than the same set for all retailers in a town.

Try to think of how it would be seen in the list of changesets by other mappers. Make it easy for them to decide if they can ignore the set, or want to examine it more closely. When it's ambiguous, then they can't tell without checking each set.

“If you need more information about this changeset you can write to me in DM and i will help you with that.”

It's better to keep it public (hence changeset discussions), for the benefit of everyone. Not just now, but in future.

This also misses the point; there should be sufficient info included when uploading the set, so that other mappers don't need to ask.

This set being ambiguous / dubious is why it's receiving comments from several mappers.

The goal, here, isn't to chastise or make you feel bad (all newbies make some kind of mistake, including those who are now experienced mappers), but to teach & learn, for improvement.

Part of it isn't your fault; the design of some editors is lacking in helping to guide new mappers (see http://github.com/openstreetmap/iD/issues/8590 ). Not that this is an excuse to exhibit poor practices.
Learning good practises is what we're trying to help with. What might come across as annoyance or frustration, isn't because of YOU personally, but that this is a recurring problem (due to lacking design, like I mentioned before).

Globe-spanning changesets will always attract more attention, because they appear in the list of more people monitoring their local area, even if no local changes were made (thus it's noise / spam to most other mappers).