Please don't delete large polygons without fully replacing it. For large edits, you need to consider how to work methodically. Eg cut it up.

As mentioned before, please don't simply disconnect `=footway` or `=steps` from the eg `highway=tertiary` roadway. This breaks routing. Aside from drawing `=footway` across `=crossing` , you still need to draw an artificial `=footway` when there's no `=service` road for the routing to coincidentally connect back. In the case of `=steps` , it also more accurately shows how it is connected, similar to how `bridge=` isn't directly connected with intersections.

`short_name=` should be used to further remove the generic form of the proper name, eg `name:en=Mun Tung Estate` can be `short_name:en=Mun Tung`

Please observe that `=bus_station` in HK doesn't include "Bus Terminus" etc generic forms in the `name=` , so this should have `name=SKYCITY`

As mentioned before, please don't merely change `=traffic_signals` + `crossing=traffic_signals` to `=crossing` . You need to create back the `=traffic_signals` separately.

Please don't merely chop off `=footway` when drawing sidewalks. This breaks routing. Even if there's no crosswalk, you need to draw a `link` / `informal` to connect it across the road. Reminder that it's not jaywalking when more than 15m away from crossing facility, and no barriers are jumped.

Please don't change `=traffic_signals` to `=crossing` alone. You should create separate `=traffic_signals` to replace them.

Please don't move features wildly. They both are a `=peak` . Don't merge them Only edit the names. You also removed `ele=` and other info.

Listing every number shouldn't be encouraged, and practiced. It's bad because imperial speed limits can use 5mph steps, causing an even longer list than metric 10km/h steps. That's described as the "majority" in USA, although the case studies hasn't mentioned yet. The `maxpseed:advisory:variable=` can be again lower, as low as 25km/h = 15mph. https://highways.dot.gov/safety/speed-management/guidelines-use-variable-speed-limit-systems-wet-weather/chapter-3
"Advisory speeds posted to the overhead signs change by no more than five miles per hour (MPH) with each change in speed, and can be updated every thirty seconds if traffic conditions warrant. The minimum advisory speed displayed is thirty MPH and the maximum advisory speed displayed is fifty MPH. If the current speeds on the roadway are below thirty MPH the signs will go blank. " https://ops.fhwa.dot.gov/publications/fhwahop12046/rwm17_minnesota1.htm
"When reductions are
warranted, VSL sign assemblies are manually activated to decrease speed limits in five-mph
increments from 50, 55, or 65 mph (80.4, 88.4, or 104.5 kph) to 30 mph (48.2 kph) depending
on prevailing conditions. " https://ops.fhwa.dot.gov/weather/Publications/Case%20Studies/14.pdf
Do we want `=30 mph;35 mph;40 mph;45 mph;50 mph;55 mph;60 mph;65 mph;70 mph;75 mph` / `=50;60;70;80;90;100;120` ? That's certainly not impossible.
As you may know, `interval=` is already used for service frequency in terms of time. It's possible VSL can be reviewed and changed in some time periods, so that it won't fluctuate suddenly. Similar to congestion-responsive dynamic tolling, or transitioning between time periods in variable tolls (something that has happened locally this year, while I'm not very interested in `charge=` yet).
What's "regular intervals"? "Interpolation" simply means how you should obtain the actual number. It doesn't mean it's exactly the same as how it works in `addr:interpolation=` . But `*:interpolation` is already used there.
The term used often as I read is "increment". But that's overlapping as used in "to indicate the value to increment between house numbers" osm.wiki/Addresses#Interpolation

This doesn't express there are only 50 and 80 possible. https://taginfo.openstreetmap.org/keys/maxspeed:variable:values won't be nice if other roads use a smaller step with a larger range.

Please read previous osm.org/changeset/153239869

Reminder: `name=` and `place=` are the existing common name and concepts in public use, not what you think should be correct or proper. Put historic names and locations in OpenHistoricalMap, not OSM. Discuss with the community, where the Discord server (https://discord.com/invite/CyG9zte) has been made available in OSM Community Index for a long time already, and there is a wiki project (osm.wiki/Hong_Kong).

Reminder: `name=` and `place=` are the existing common name and concepts in public use, not what you think should be correct or proper. Put historic names and locations in OpenHistoricalMap, not OSM. Discuss with the community, where the Discord server (https://discord.com/invite/CyG9zte) has been made available in OSM Community Index for a long time already, and there is a wiki project (osm.wiki/Hong_Kong).

Reminder: `name=` and `place=` are the existing common name and concepts in public use, not what you think should be correct or proper. Put historic names and locations in OpenHistoricalMap, not OSM. Discuss with the community, where the Discord server (https://discord.com/invite/CyG9zte) has been made available in OSM Community Index for a long time already, and there is a wiki project (osm.wiki/Hong_Kong).

Please don't change the entire `building=` area. Create a separate new point inside.

2. And please, more descriptive upload comment, at least and quite enough a general location. Doesn't have to be exact, precise, and accurate. "NT" is still better than nothing. Shatin is already well satisfactory. ,

Please don't blindly add `=crossing` on every `=service` . Worldwide, it's usually not added for flat ones .

Can you stop fiddling with the data. You have cause enough damage. Please explain what you are trying to do, and ask for help first.

Lack of reacts doesn't mean one part of a comment is good or bad. I described many issues, with my opinions. Others don't have to agree with all of them.
"However, this does not mean "feel free to ignore existing tagging schemes " osm.wiki/Any_tags_you_like

Please don't use `historic=tomb` if it's not known to be `historic=` . Use `cemetery=grave`