Please don't use `=apron` for what's not an entire apron, or draw arbitrary areas. This duplicates the `=parking_position` line.

Please don't add descriptor labels to `name=` , which is for proper names only. This is not a printed paper map. They are harmful to a geographical database. `=aquaculture=` etc already expresses this.

`level=` should not be changed to `layer=` inside `building=`

In this case, it would be more straightforward to argue it's not `covered=yes` from how narrow and curved it is. But other cases, some users may find splitting `footway=sidewalk` to add `covered=yes` easier than drawing the entire `man_made=bridge` , then you have to ask why should the roadways not get `covered=yes` together.

In Germany, someone used 1 `covered:by=bridge`

It depends on what you mean by that. Certainly drawing a `building=` doesn't prevent `covered=yes` from being added.
The issue is there's no differentiation on when you should do that, and for long or wide bridges. Walkways can be specifically designed under viaducts to be sheltered. Then you have an arbitrary distinction on why roadways shouldn't get it.

Why did you delete a sidewalk section?

These don't show the exact reason, but it's critical for `*:lanes=` when `destination:ref:lanes=` and `destination:lanes=` have freeform text in `ref=` and basically `name=` . Using `none` would be interpreted literally as a `ref=none` or `name=none` there, so 0-length must be used.

I don't know what's the origin or authority, but it's used in `destination:*=` destination:symbol=*#Destination_with_multiple_symbols

Please don't delete directly, as this contains an address, and represents a shop space for tracking and updating. Change it a plain "point", or "vacant shop".

2. Please don't move unrelated features to a `=footway` . That's not realistic, and makes editing more difficult.

Please don't delete `shop=vacant` . Its purpose is exactly to record a shop space for tracking and updating later.

The `=no_left_turn` was wrongly set as `=only_left_turn`

`=private` means individually allowed. which is not the case here. Events accept anyone willing to pay (`=yes`) , so should be `=customers`

There are 2 `architect=` here, one without Wikidata. Emptiness is the standard format for indicating absence in such text.

As said many times, please don't make random edits especially deletions to attempt to fix a software issue. You should investigate the software, not fiddle with the data.

Please don't directly delete them, as they still represent a shop space. It makes tracking and updating them more difficult. Others may contain addresses and other info. They should be changed to a plain "point", or "vacant shop".

Refuge islands should not be changed to `=crossing` footway=traffic_island

Please don't use brackets. `name=` is for proper names only, not a descriptor label. This is a digital map database, not personal or printed paper map.

1. The roads are kept because the ingress and egress will be the same. I don't know if the bus terminal will be changed to sawtooth layout, but parallel stands seem likely for this small size of intermediate stops.
2. The `addr:housenumber=` should be kept as they still exist, and would be reused somehow
3. It's usually not a good idea to draw the exact layout of the construction site in the status you find now, as OSM is not about recording construction progress. There will only be one continuous site with 2 towers, the Low Block extending from Kwun Tong Rd to Fuk Ning Rd