Welcome to OSM, and thanks for your contribution. You dragged a road pretty far in this changeset. I fixed that for you, but please be careful!

Welcome to OSM, and thanks for your contribution. We normally try not to use name descriptions like the name you added - there's a massive amount of tags that you can read about on the wiki, like the barrier key:
barrier=*

In this case I already tried to add all the service roads and gates. Maybe you can confirm that this edit was correct, if you have a chance?

welcome to OSM, and thanks for your contribution. You replaced the traffic light node with the ALPR tags in this edit - I have fixed that for you.

changeset/172854498

This looks like it's in the wrong location as well.

You dragged a sidewalk in this edit, please be careful.

source tags carried from previous edit, sorry!

You added these on highway intersection nodes. Please do the built-in editor tutorial and try again

reverted

changeset/172760247

You added these on highway intersection nodes. Please do the built-in editor tutorial and try again

reverted

changeset/172760247

There are revert tools which can help undo these changes - is it all changesets you made with "NERF" or just some of them?

Do you know what the license is for the speed limit data from Mapbox? I'm concerned that it isn't compatible with the OSM license.

You added the business to the entire building. Please add it as a single point at the approximate location in the building.

changeset/172720582

You didn't actually change any speed limit values in this changeset, it just bumped the version on a bunch of the ways. Can you tell us about your sources and the editor you are using?

What is "GOAT MAN"?

welcome to OSM, and thanks for your contribution. natural=grassland is for naturally occurring grasslands - for maintained lawns like this consider using surface=grass

natural=grassland

Also, please don't draw a lot of tiny areas like this - it should be one object for each section of grass.

alt_name is used for a different name used to refer to this specific feature - I don't really think that applies here. Nobody says "Austin" when they are referring to Jollyville specifically. Austin is already represented well on OSM by this relation

relation/113314

these look more like highway=footway than highway=service. They aren't wide enough for a car

Welcome to OSM, and thanks for your contributions. It looks like you have made a few edits where you added a name like "new italian resteraunt" - on OSM, we generally try not to use descriptive names like that. It's totally fine for an object to not have a name, even if it's just because you don't know it yet.

These don't really match up with the footpaths that are visible on imagery. If you switch to Bing imagery, it's much clearer.

using a descriptive name like "LJ Childcare Drive Through" is normally not desirable - I fixed this for you, and also marked only the section that goes under the awning as one-way based on the two-way markings on the north-south segment.

Welcome to OSM, and thanks for your contribution. On OSM, tagging needs to follow a particular format for data consumers to be able to use them. You can read about it on the wiki
osm.wiki/

In this particular case your "Made by" should be replaced by

manufacturer=Flock Safety
manufacturer:wikidata=Q108485435

we also don't normally explicitly document unknown information like this - that is implied by the absence of a key.

Let me know if you have any questions