I've added bicycle=yes to crossings

Hi, was there a street sign on the ground or how did you determine this road name?

Hi, consider not mapping private backyards (sauna, trampoline)
osm.wiki/Limitations_on_mapping_private_information

I also see "Distance in property description is calculated using © OpenStreetMap", but the key word here is "distance". I've checked and distance to Rooslepa Beach, which is mentioned on booking, directly is 3.7km, while booking says 2.8 km. Maybe the data about beaches is not from OSM or Google. I hope booking support helps you!

Hi, I've checked it out

1) Roosta rand is already tagged correctly on OpenStreetMap. I'll remove your changes.

2) The search bar on this page

https://www.booking.com/hotel/ee/villa-hanson.et.html#map_opened-hotel_surroundings

does requests to Google's API, not OpenStreetMap.

3) On Google Maps this place is called "Elbiku rand" and is marked as a hiking area.

4) I suggest you select it on Google Maps and use "Suggest an edit" button at the bottom to change it's type, and, if "Roosta rand" is a more correct name, then a name too.

5) I don't know how much time will it take for Google to accept it, but also be aware that even after it's updated in Google Maps, booking.com may not update the beaches nearby data from Google automatically or fast enough.

Wow, those trees. I'm not sure about removing natural=wood though. Trees and the forest are not mutually exclusive. The same as you can map individual trees in a tree row but it doesn't make the tree row redundant.

Some clients may ignore trees or display them only at higher zoom levels.

You've also named one section
just "Tammermaa". I assume it's by mistake.

It's usually better to tag forest paths as highway=path ("Path" in iD editor template selection) unless there is an explicit ban on bicycles there.

The beach is already added and has an appropriate name. Is something missing in your opinion? What did you want to achieve by adding this name here?

Hi, I recommend to check if
tourism=guest_house
is applicable so that it won't be just a building with a name.

You can add
tourism=guest_house
in the bottom of the left panel, under Tags when the building is selected.

Hi, you've accidentally connected Lepistiku park's footways to Tammsaare keskus. It sometimes happens, but when you save the changes, please review all the warnings before submitting. I've fixed it.

Hi, are you sure that your name correction is correct?

"s" is often transcribed as "з" in Estonian to Russian transcription, when the "s" is between the vowels.

https://www.emakeeleselts.ee/wp-content/uploads/2020/06/eskt_otsus_2008_ttab.pdf

Thanks for noticing! I've removed this whole building part, looks like I forgot to remove it when I split it into two other overlapping building parts.

Hi,
1) Since you've already added business as a node, you don't need to add a name for the building.

2) This looks like a legal address. Is any activity done on this address? Doesn't it need to be on the map? OSM is about geospatial data, there is äriregister for keeping a registry of legal entities. Seems like there is also another business registered here this way.

3) If it is useful, the node probably needs an office tag office=* . Otherwise there is no way for data consumers to understand what it is.

:conditional seems to be a key suffix you can attach to existing key to either change the default value or in some cases just show at what condition it's 'yes'. For example
parking:maxstay:conditional=xxx or access:conditional=xxx

"parking" key is used to describe parking types, so while parking:conditional is possible, it could be used to describe a change from "on_kerb" parking to "lane" parking at certain conditions, for example.

Hi, as I understand, based on the same table, the tag should be
restriction:conditional=no_parking @ (Th 10:00-12:00)

There doesn't seem to be a tag named parking:conditional, there is parking:condition, but it's deprecated.

Hi and welcome!
The local (Estonian) name should also be added as default name.

I agree with Pikse here. I wanted to write something like this, but was too lazy to formulate it in such a clear way. The fact that teeregister adds "tee xx" to adjacent road names in other places shows that there is some inconsistency here and IMO it's better to just follow Maa-amet here. Unless street signs on the ground explicitly say differently.

You also can notice that the street itself has no name there.

IMO we should avoid creating a "tree"with branches for streets and try keep them as a simple chain unless official data/street signs say differently.

This is a name of a cadastral unit also containing "L3" in it's name. It doesn't have to be tied to a street name.