Just to make it clear, when mapping, one must *never* refer to either Google Maps or Streetview, as OSM has no permission to use them and they are copyrighted.
What is legally available is the different background imageries -- ESRI shows some things, Mapbox here even better -- or permitted ground-level imageries, or personal knowledge. (Probably select government resources as well)
Apologies if you have not and just mention them as a refernce in context of this discussion, but I wanted to make it clear in case questions arise later.
That said, in the shadows, I can't make out quite what's going on here either.

I see, you added the aisles anew as v1 by hand.
I was worried I was imagining things, or that the summary below can be easily fooled, as apparently object histories can be fooled in this web interface by a Vespucci user.
Sorry...

Sorry, nevermind, I should read everything first

Not quite, Paul.
Georg removed the coloured road lettering, but it wasn't a complete revert -- the parking lake remained intact to be scribbled on again, and the removed parking aisles (lake isles?) weren't restored.
That Guy then built on that a second time, but I suspect the DWG may get involved with a full revert of all three changesets.
Maybe I should, instead of sleeping Real Soon Now

Heh. You do know about the TIGER 2017 names background layer?
That has this one included there, so no need to bother Auntie Google, nor Orlando (save to verify TIGER is correct).
Often TIGER will have errors, but there are a *lot* of new developments lacking names in OSM, but which are listed in the TIGER Census data already.
Hope that helps with your adding more missing names, a worthy project I've done when drawn to my attention.
Keep up the good work!

Sorry to bother you again. but can you mention the source of your names in your changeset or the data itself?
I see we have all these names listed in our legal background layers, but in case of questions, it's best to be certain.
Thanks!

You do realise that OpenStreetMap may not copy or import any information from Google Maps or Streetview?
That is what it sounds like you have done here, which is not permitted, and further, OpenStreetMap will not allow this information to be included. It is a violation of copyright, and does not respect Google's intellectual property rights or their investment in obtaining and maintaining their database.

Hallo Ivan,
In this and other changes, you have changed a named Creek, tagged as a stream, into a full-scale river.
However, the aerial imagery I see does not back up this claim at all, with the water width, if that is actually water, at times not even being a metre wide.
I do not believe something officially named as Ross Creek, should be tagged as a river in OSM, which is reserved for much larger and permanent waterways.

Sorry, but Robin has added useful information to improve the OSM data, and even if you may consider it redundant, this information is important to someone with different cultural expectations.
I would tell my family what they experienced, that they cannot pay with credit card in many places, and that nowhere can they pay with only a mag-strip card without Chip-and-PIN.
They told me where they come from nobody pays cash anymore and it's often not accepted.
OSM is an international community effort, not a company marketing platform, and if it is important enough for the community to add factually correct info about any shop in your chains, you should respect that.
Even better would be to list which credit card and payment card brands (V-Pay, Maestro, Electron, American Express, and countless others) are accepted, or if cash in a non-native currency (CHF, USD, and so on) particularly near shopping-holiday borders.
That is the sort of information OSM builds upon, and not just the local defaults.
You will find that the OSM community encourages new contributors to add as much detail as possible, and to improve upon existing data.

Hallo that,
Note that what you are doing is considered vandalism.
OpenStreetMap is a serious project that sees wide usage, probably by the very agency whose car park you've chosen to desecrate. As such, with thousands or millions of data consumers relying on OSM to deliver factual and accurate data, you risk being banned from the project for this behaviour.

Mostly road and building geometry shifts around the rail lines, or by the baseball park.
Some pretty gnarly looking admin boundaries.
https://overpass-api.de/achavi/?changeset=55910930
Reverting this would lose a car park, but otherwise the damage should be minimal.
.
Your first changeset,
https://overpass-api.de/achavi/?changeset=55910035
is so trivial at Burger King, I don't know if you even want me to bother, or if you want to move both buildings yourself against Mapbox.
If only you had stopped there :-)
.
Let me know what you think about these four remaining changesets, two of which I'll happily do (or three), one of which I need to think about something else for a while.
Which is what I'll do, is take a short break.
.
This takes you back until just before 22h GMT on 30.Jan.2017, when you started.

This changeset has been reverted fully or in part by changeset/56069985 where the changeset comment is: Undo misguided alignment to newer satellite rather than aerials

Shifted buildings, again in the southwest of town.
https://overpass-api.de/achavi/?changeset=55912006
Shifts to the interstate.
Less original content.
More iterative changes to the admin boundary.
This looks easy enough to revert and restore to normal. But I could be talked out of it.
I will study the final two candidates first, and debate if I want to sleep on it after all the biggest ones finish and you can study how things are.

At first glance, I think I will pass on reverting this one.
https://overpass-api.de/achavi/?changeset=55912715
There are some shifted roads and buildings, but concentrated around Pioneer Park and the interchange, and I see more additions and deletions to be shifted.
Admin boundries are touched again.
.
If you disagree, you can try to talk me into a revert - it won't be hard.
I just want to be awake to look at things.

Roads again.
https://overpass-api.de/achavi/?changeset=55914296
The park (should be untouched after your fixes) and the nearby river.
The elementary school.
Some buildings.
Here you create and you modify admin boundaries.
I think the benefit of shifting things back into position is worth the pain here too.
After the revert, paste the following changeset number into the achavi URL to see just what changed.
The one in progress is showing a number of failures, as expected.

This changeset has been reverted fully or in part by changeset/56069695 where the changeset comment is: Undo misguided alignment to newer satellite rather than aerials

roads, some buildings, quite a bit of river work, a few admin boundaries touched.
Further improvements will get lost.
Perhaps the riverbank improvements can be recovered.
Golf course changed from v1 here, but shouldn't be touched.
The building and road shifts look like they make the revert worthwhile here, so off I go.

https://overpass-api.de/achavi/?changeset=56069252
shows the damage.
Golf course untouched, most admin boundaries untouched, maybe (but one got quite messed up).
Your carpark at the courthouse got deleted. I converted your newspaper office into a Pizza Ranch. And so on.
I will later analyse the logs I kept this time.

This changeset has been reverted fully or in part by changeset/56069252 where the changeset comment is: Undo misguided alignment to newer satellite rather than aerials

This changeset has been reverted fully or in part by changeset/56068613 where the changeset comment is: Undo misguided alignment to newer satellite rather than aerials