Please don't copy the project title. This was already correct. `name=` is for proper names only, not a descriptor label. It should reflect what is being constructed finally. Prepositions, commas, addresses, and brackets etc are inappropriate.

This causes a conflict with the correct `addr:housenumber=` + `addr:street=` of the estate `landuse=residential`

Please don't use `addr:housenumber=` if it's not numbered by the street or village. `addr:unit=` is a possible choice.

1. Yes, I added a `=platform` back
2. No, that's the `railway=tram_stop` + `public_transport=stop_position`

Please don't remove the tram `=platform`

Oh, and you should learn about the limitation of SRTM or whatever DEM those maps are using, and the contours or hillshades they generate. Vector breaklines exist independently from raster elevations.

Have you replied here you annoying hypocrite? changeset/144534922

Can you stopping being so childish to use other users' changesets to nag about your personal feelings? Are you a single bit organism that can only think about dichotomies?

Yes, and you are well know for holding a grudge and commenting on other's changesets randomly. You must be blind when I cite how `addr:street=` has been used worldwide.

Please don't move `=kerb` to the connection at the sidewalk. This doesn't reflect reality.

Can you please stop casually deleting random things? You removed a `=bus_station` here.

It's preferrable to not delete things even if you are working on them. Eg you deleted node/2441045168 outside TST East BT without replacing it. Maybe you forgot, but for organizational and tracking reasons, it's not desirable. Certainly the result was deterimental there.

Please don't delete then recreate the same objects. Simply correct them by adding the tags needed.

1. The section outside the bus terminal is roofed, not inside podium. Please don't delete and merge sections arbitarily. They are split for reasons.
2. Please don't delete lifecycle-prefixed `disused:amenity=` . If you don't want to update them, leave it.
3. Please don't delete `crossing=no` points as they show where there isn't crosswalks.

By this criteria, another person could equally change your slashes back to semicolon because it's a common mistake and deviation from standard. While I personally prefer uppercase for abbreviations too, I have to consider lowercase is the standard practice, and abbreviations itself is frowned upon in the first place.

Having slash as the punctuation used in text doesn't mean OSM should use it for the data. An application could even generate these labels automatically. So you admit it's another undiscussed re-tagging?

You didn't even change airmark=beacon#Examples

Where have you gotten approval for re-tagging the standard semicolon multival pattern to a non-standard style? Except the page you created this week osm.wiki/w/index.php?title=Tag:beacon:type=VOR/DME&action=history
While both have jumps in 2017~2018, semicolon seems to have more steady growth https://taghistory.raifer.tech/#***/beacon:type/VOR%2FDME&***/beacon:type/VOR;DME
osm.wiki/Proposal:Radio_navigation_aids is from 2012. It's using `type=` , which shouldn't be used.

Please don't delete info with obvious mistakes that can be corrected https://www.topshoulder.com.hk/contact-us.html

Please observe carefully. This is the main route of Castle Peak Rd via Shui Pin Wai Interchange to Yuen Long Northern Bypass due to restricted lane change.