Please describe what you changed and why in the changeset message. For example, "Added road name." Here is a link with more guidance and examples: osm.wiki/Good_changeset_comments

As I understand it, the "covered" tag simply indicates that some type of cover exists over top a road segment. It's still necessary to describe *what* is on top of each part of the map, and in what order, and the "layer" tag should be used for that. So I feel like the prior tagging was correct.

For this one you've tagged the whole office building with data center tags, but it looks like there are other offices inside as well. If so I think it would be better to keep the data center tags on a node or maybe a indoor=floor.

Please don't connect landuse areas directly to highways, it's inaccurate and difficult to edit. osm.wiki/Tag:landuse%3Dresidential#Separation_from_roads

Are you sure about this? I was under the impression that highway=busway is only for BRT roads, and service=busway should still be used for bus-only service roads, like the ones here.

Copying data from Google Maps, including Street View, is illegal: osm.wiki/Google

I've deleted your contribution. Spam is not welcome in OpenStreetMap.

It's often better to just remove the tags of a closed business rather than delete the point entirely, since some information like the address might still be relevant.

Welcome, and thanks for your contribution!

Please respond to my previous comment before continuing. You need to have a descriptive changeset message, and MVPD organizational boundaries are inappropriate for OSM.

Please use the changeset description to explain what you changed and why. There's some advice on this page: osm.wiki/Good_changeset_comments
In the US, "admin_level=10" is meant for incorporated neighborhoods, but the name you've chosen for this boundary makes it sound like some police department's organizational area, which is not appropriate for OpenStreetMap.

Please save your changes before moving on to another area, and please keep HOT project changes within the area of the task.

Hello and thank you for contributing to OSM! In the future, please save your changes in one area before moving on to another; this keeps the total changeset size small and therefore easier to review.

If you use JOSM, the Java OpenStreetMap editor, you can download data, edit it, and save it to a file, then open this file in your program.

Yes, that kind of description is good! Even though I can click through to see what objects you changed, it's not always obvious what you changed about them, and it's helpful when reading through long lists of changesets to know what each of them changed without actually clicking through (otherwise, the changeset description would be useless!). The wiki page I linked goes through these and many other reasons why descriptive changeset comments are useful.

Make sure you're looking around for duplicates before you add something! The building was already tagged with the shop information.

In this changeset you removed one lane from turn:lanes and vehicle:lanes on Berryessa Road, but did not remove the lane from bicycle:lanes. Please make sure that ALL values with key ending in :lanes have a consistent number of lanes. Also consider if by removing a lane you are removing information. Here, you removed the bike lane, removing the information that it is to the left of the turn lane.

Could you please try to be a little more descriptive about what you changed any why? Like if it was road realignment, lane tagging, new building traces, something else, or some combination. Here are some more suggestions: osm.wiki/Good_changeset_comments Thanks!

Please save your changes in one area before moving on to another, to keep the changeset size down. Also, please use the changeset description to describe what you changed and why; for example, "Added parking lots and service roads". More examples here: osm.wiki/Good_changeset_comments

Please remember to save your changes in one area before moving on to another, to keep the changeset bounding box small.