Thanks for the reply. I already fixed the tags that where added up to now. Just make sure your presets / auto-completion get updated.

Hi,
please check your tagging:
It's "axle", not "axel".
and the full tag should be
"maxaxles:hgv"

Hi,
could you check this parking? "maxstay" should be a time, not a price.
way/1383240422

Hi,
you added two memorials with a huge amount of text in the tags. Is all this text in the various languages actually present on the memorial? If not, it shouldn't be in OSM - a link to Wikipedia or Wikidata containing all the details about the person is sufficient.

It's described in the wiki page about ferry routes:
route=ferry
Are you familiar with bus routes? The mapping scheme is almost identical.

You can just draw one way and create two relations using this way.

This separates the two types of ferry without drawing anything twice.

Hi,
please check the wiki for common socket:* tags - the ones you used here are not used in any other place.

Hi,
you used tags like "level:1-2=residential" to mark the use of different parts of two buildings.
Usually, this is mapped using two building:part=yes objects with their respective building:use tags. Could you have a look at this tagging scheme?

Hi,
these ferries got a huge amount of tags that are not used in other places and are very unlikely to be used in any kind of software.
I'm convinced that there are enough standard tagging options for this kind of information.
Most importantly, the prefixes 'public_boat' and 'private_boat' need to be removed. There's no need to have the information of two different services on the same way - just separate them into to ways. That would make the information a lot more clear immediately.

Hi,
you introduced a new tag here: "bikestreets" - what does it mean?

Hi,
you introduced a new tag "mayoral" here - what does it mean?

Where did you find this definition of the output?
The Wiki clearly says
"charging_station:output=<xxx> kW – Use this to specify the maximum output of the entire station: This value can often be found on the back of the charge points. For a station with multiple charge points, add them all together for the entire station maximum ouput."
amenity=charging_station

A matching station with a high enough output on a specific socket you can find by looking at the socket:*:output tags.

It's not useful to tag all the sockets that don't exist. Did you check if there is really no socket:cee_red_63a available? Just add the sockets that do exist.

Hi,
you added the new tag "station_deux_roues" here - what does it mean?
node/12794145071

And: Are you sure the output of this station is just 22 kW? That's not really enough to charge 6 cars in parallel.
And: the station is taggd to have no sockets at all which is clearly wrong. Please don't add "socket...=no" tags, just add those that exist, including their count.

Hi, I didn't add any data, this was done in another changeset.

Hi,
please check this street, something went wrong with the parking tags "par" and ":taxi".
way/143057430

Hi,
you used some maxstay and charge tags here that don't seem correct.
E.g.node/7673202253

Checking the pricing scheme of the operator, there is no maxstay, but just a fee if you stay longer than a certain time.

Also, the price doesn't seem to be right for this high-powered charging station.
There's no low-power connector available, so there's no charging below 0.78EUR/kWh possible.
The prices also don't change depending on AC or DC, but just on the power available.

Lastly, I would not tag the charging prices - they tend to change way too often and depend on way to many factors to be maintained in OSM. Just link to the very simple and concise document of the operator.

Hi,
the tags
access = per_ipovedenti
segnaletica_accessibile = Sì
are not commonly used. Could you explain which infrastructure is existing here that helps the blind?

Hi,
please don't try to dump data from an external source into OSM.
All these tags should not appear in OSM:
block=-1
color24=-1
colour=0,0,0,7
etype=18
handle=896
linewidth=0
ltscale=1
lweight=-1
name=TRACKER
ocolor=256
olinetype=continuous
space=0
thickness=0
transparen=0
visible=1
width=0

Also, your user name and the 'operator' tag suggest that you are doing these edits somewhat officially. If so, the "organised mapping guidelines" may apply:
osm.wiki/Organised_Editing_Guidelines

The tags along with the accuracy also make it seem that the source (Ortosat) might not be correct.

And lastly, you added fences on top of existing tracks, blocking them. Please check which of the objects is in the right position.

Hi,
please check the wiki about how to map charging stations.
None of these tags is correct:

charge-capacity
charging_capacity
charge_capacity
num_stations
num-station
num-stations
num_sations

amenity=charging_station#Examples

That's not access=permissive - that means that someone tolerates people accessing the way without asking, but has can revoke this right at any time.

access=private would be appropriate - someone decides on a case-by-case basis who is allowed to enter.