Please don't use change `bicycle=` from `=no` to `=use_sidepath` when there is no `=cycleway`. Legally, you are not allowed to bike on sidewalks.

What I do is move this label to `description=` . Use `name=` for company and route number only, similar to the Schedule of Routes. The direction can be obtained in `from=` and `to=`. That's why I add `from:*=` and `to:*=` languages.
In the status quo, it is common to have `name:en=` and `name:zh=`, but not for `from=` and `to=` .
It is very tedious to update routes when you put all the info in `name=` . I said screw it when I have to update Tuen Ma Line and East Rail Line

It just works poorly in long descriptive cases.
6 osm.org/relation/9383262 osm.org/relation/6517616
89D osm.org/relation/16227456
There are 114 `route=bus` with `name=` longer than 100 chars. These 5 exceeds 150 chars.
682C osm.org/relation/1290051 osm.org/relation/1317095
HZMB (because tri-lingual) osm.org/relation/8858065 osm.org/relation/8858068
788 osm.org/relation/10866299 osm.org/relation/10866300

I would like to remind this is bad style anyway. It's Tagging For editing software, inconvenient for applications to show route name and directions separately. iD already supports generating labels from `from=` and `to=` , as well as `network=` . osm.wiki/Talk:Buses#Bus_Route_Naming

1. Please don't delete the `place=`, It's a different concept from other features.
2. Please don't add village names to `landuse=residential` . A village can include other named housing estates. Use `addr:village=` only.

`=canal` is used on `bridge=aqueduct` , which would be used for water supply as well. A catchwater doesn't carry excessive useless water away, unlike drainage tunnels. It intercepts the streams to redirect them to the reservoir, or even the Settlement Basin here directly. The water hasn't become useless, as it will never reach built-up areas.
Also an unlined "ditch" can be used for irrigating rice paddies and farm fields, especially in Asia. But `=ditch` is for drainage only. So the words shouldn't be taken literally. At least in HK common language, "canal" usually refers to water channels for ships, not irrigation channels common elsewhere and used for `=canal` in OSM.

I'm actually considering changing them to `waterway=canal` because it carries water to the reservoir. So not useless water.

Please use `addr:full=` if you don't know how to split the address. Don't remove the `addr:housenumber=`.

1. You should be removing the few "no" in https://taginfo.openstreetmap.org/keys/fax#values and https://taginfo.openstreetmap.org/keys/contact%3Afax#values instead. `no:*=` is somewhat used, and documented.

1. The significance here is all other branches in the area has a fax. This doesn't yet, apparently.

2. Please use descriptive upload comments.

https://taginfo.openstreetmap.org/keys/contact:name has already been used nearly 200 times. This person is for the mobile only. Other details refer to the shop. Deleting it doesn't solve anything.

Please tell me how to indicate a feature has no fax number. Deleting it doesn't solve anything.

`drain=` has already been used for different purposes https://taginfo.openstreetmap.org/keys/drain#values

`disused:*=` is for services, functions, and activities. If the physical structure still exist, it should use `builiding=` + `disused=yes`.

Please don't delete this. If the meaning doesn't fit, it should be changed to other features. But the geometry is the same.

Please don't change `=mini_roundabout` points to `junction=roundabout` lines. This is misleading. It is still transversable, not raised.

The covers are not yet removed. And your locations are wrong. They should already be added.

Please create a new object. Don't modify others.

3. Please press [Q} to square the building corners.