It seems to me that 99% of landuse in this changeset could second as toilet... To be more serious though, please try to keep your changesets local. Aswell as using the comment feature to actually describe what you changed. Happy mapping!

Reverting now isn't necessary don't worry. It's only when I'm working on one changeset that the elements I'm editing being edited by someone else before uploading can mess things up.

Yes! This element specifically should indeed stay a polygon and is perfect as is (: Good job.

I think you might misunderstand how multipolygons work. It shares a side with it because you made it have one. If you add a non multipolygonal area, then add another one exactly the same way and make them share just 2 nodes you can see how they connect. The same connection will work for how many nodes you want connected. See for example how way/1240782808 is connected to it's neighbour. Both are non multipolygons sharing an edge! Mulyipolygons are only needed with ways with 2000< nodes, or with holes in it.

Misclick on enter :P
"Editing landuse and path"

osm.wiki/Multipolygon_Examples
This page explains it very well. But for example relation/20440282
Could work just fine as a singular area (:

Nicely done!

Heya (: Welcome to OSM.
I'm glad you've edited here. Feel free to join the vibrant community on discord or slack.
https://discord.gg/openstreetmap
I would like to add that changeset comments are supposed to what changed specifically. A comment like "Added parking" would've been much more usefel here.
Happy mapping and have a great day!

I've re-added the deleted tag. I'm not experienced in boundary tagging so forgive me if I'm wrong in that.

مرحباً محمد
What exactly does "Important changes" mean?
As far as I see you've updated some names but also removed a tag which doesn't seem that it should be deleted. Was this an accident?

Hello (: May I ask why almost all your changesets have so many multipolygons? You often have areas which could be enclosed by a single way with an uneccessary amount of ways or areas all over the place as a multipolygon which is rarely the best approach. This is very annoying to map with in the future. Especially in iD.

Kind regards
Tomas09

Heya! While it definetly isn't your fault since there's no way you could've known. I'm mapping this area currently but not yet removing some overlapping areas as to not delete tons of still valid landuse. I'd like to request if you could avoid changesets like this one here as this reallllyyyy messed up a pending changeset :P

Accidentally used the wrong description whoops. "Fixing broken multipolygon"

Ik zie altijd alleen maar de engelse termen. Zeker weten dat dit zo is?

Well done (:

Hello! Is there a source for this? All aerial imaging sources dont show there being a named feature here. This combined with the fact you're a new user makes me want to ask this. If you don't understand what's wrong feel free to ask me what you don't understand.

JOSM AI helper plugin I believe

Only 2-T974-7

Fixing `landuse=bare_rock` and coastline issues*

Sorry for the untagged ways. A JOSM plugin had a bug and I had to either restart JOSM without saving or upload the incomplete changeset /: