2. The `=cliff` split were correct in separating. `=embankment` shouldn't enclose the whole section. It's for the slanted slopes on the western and eastern sides only. North and south ends should be `=retaining_wall` for vertically.

`level=` shouldn't be added to `building=`

Don't use brackets as descriptor labels on `name=` , which is for proper names only. Use `alt_name=` + `ref=`

Please don't delete it, as it contains an address. Change to ` was:amenity= ` ` disused:amenity= ` / ` abandoned:amenity= `

You are still mixing `=informal` and `=unmarked`

3. There's no need to blindly align exactly to some imagery at some version. There will be offsets. Eg it matches old Esri Clarity.

0. Please use descriptive upload comment
1. Please don't delete then redraw the same feature. Move them.
2. Please don't remove details

Slip roads `=bridge` should not be drawn parallel. It should follow joints, with perpendicular ends. Except perhaps eastbound expansion, but it's stitched together already, and jointless above.
It's exactly difficult to define what's a `=bridge` for an elevated road with many slip roads. The `layer=` is worse enough. (They shouldn't suddenly end at the `=coastline` either)

You made conflicting layers. Slip roads passing below `layer=2` IEC is `layer=1`

If you want to do phased openings, you need to use `construction:junction=roundabout`

`name=` is for what it would be after completion. Not project or contract title, which are descriptive labels.

Please don't artificially compose names. `name=` is for proper names only. They are already added separately inside.

Can you stop promoting small, sparse, lightly populated, insignificant villages with no own facilities? That's one reason why `=suburb` is used to distinguish between distinct villages, and large areas.

If you want, you might try `addr:housename=` , but that will be opposed for not being a postal address. While `is_in:housename=` is often misunderstood as deprecated, here it's indeed unneeded as there's a spatial relationship. You shouldn't add such attributes to `=fitness_station` , `=pitch` inside either.

Don't add the same `name=` to `=playground` inside a `=park` (where there can be multiple of them, as it's used similar to `=pitch` for patches of playgrounds)

Might be an SC bug. But I can't imagine why it does this. Need to test the app on Android.

Be bold in what you create. Be cautious in what you change. https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_fence
"It is important to understand that warnings are just warnings, they should be examined and fixed where possible but never at the cost of introducing wrong data. Some validators warnings are generated for valid data. Often in such cases validator code should be fixed, not OSM data. Sometimes false positives are unavoidable. " osm.wiki/Quality_assurance

You did cause damage by removing the `building=` there. I'm pointing this out. If you don't want to read them, ignore it. But don't complaint if others change your work.

0. Please use descriptive upload comments, or split your changeset
1. Please check that `building=` is not removed for buildings when adding `=pumping_station`

And you still made it inconsistent, as there are `*:suburb=`