Did you forget to put a name on the locality you added (node/4953767238)?

Something went badly wrong with this edit -- you appear to have re-used a node from Indonesia for your waterfall. I've reverted it.

Is there a reason why you're calling Friday Avenue/River Street through Mullan a "primary road"? I drove it last Saturday, and it's a very minor road through a very minor town -- the general feel I got was that it should be classified as "tertiary". It's a narrow low-speed two-lane road lined mostly by houses, going from not much of anywhere to not much of anywhere.

Are you sure about the non-existence of Humbert Airport? The DigitalGlobe Standard imagery (the newest available for this area) shows a line of ground parallel to the nearby field with a worn look to it, and a structure at the north end of that line that could be a hangar.

Keeping the number of changesets down is okay, as long as the changes are grouped into a small geographic area. "Cleaned up all the old airports in Pike County" is fine; "cleaned up a hundred old airports scattered around the United States" isn't. Unfortunately, Maproulette gives you the latter.

Best practice for indicating a business is closed is to prefix the "shop" tag with "disused:" (for example, "disused:shop=doityourself"), and to do the same with the "name" tag if the signs have been removed. If the signs are still there, leaving the "name" tag alone means that people can still use the building as a landmark for navigation.

What you've done will be interpreted by computers as meaning there's a do-it-yourself business there by the name of "Vacant".

Standard practice for schools is that the name goes on the school grounds, not on the school building, except in unusual cases such as two schools sharing a campus, or when the building has a name different from that of the school.

Please don't make up names for things.

It looks to me like the towers were already mapped. Is there some reason why you're adding them again?

The "name" field should only be used for actual names, not descriptions. For example, it's obvious that a walkway is a walkway because it's tagged as "highway=footway".

What are you trying to do that involves drawing large, untagged outlines?

Please don't abbreviate names. It's easy for a computer to decide it needs to shorten "Lane" to "Ln" if it needs space; it's much harder to decide if "St" should be expanded to "Street" or "Saint".

Looks to me like you got everything.

For situations like this, where you want to simply revert everything, the best tool is probably JOSM (https://josm.openstreetmap.de/). You'll need to activate the "Reverter" plugin, which will give you a "Revert changeset" menu option in the "Data" menu. Enter the number of the changeset you want to revert, make sure it's doing what you expected, and upload the resulting changes.

The "name" field should only be used for names, not for descriptions. Something like when a building was completed would go in the "start_date" field.

What are you testing, and since it pretty clearly didn't work, are you planning on reverting it?

What TIGER data have you deemed unnecessary here?

Additional imagery used: DigitalGlobe Standard and NAIP Washington 2015.

This isn't a park, it's a couple houses.

It looks like you're taking out far more nodes than you intend. For example, way/409571420 went from 72 nodes relatively evenly spaced over three miles, to just eight nodes, with a maximum gap between nodes of 2.25 miles.