Why did you add I 380 under name=? Please read osm.wiki/Interstate_Highways and revert this edit. Thank you!

I see what you're going for here and I think the intent is awesome, but the name= entry is for the actual signed name. This is overriding some actual names used in giving directions and does not meet OSM standards. However, a route relation would be an EXCELLENT way to represent this!

Please undo this edit and add the route relation. Thank you!

Fixed.

Original Lincoln is the name of the neighborhood and zoned areas. (Not the most original name, admittedly!)

Fixed. There doesn't seem to be a good way to simplify that wouldn't result in a reduction of data quality, unfortunately.

West of Downing Street is not open to traffic yet. Please revert.

Huh. Didn't know you couldn't add a label to a multipolygon. I suppose boundary will be a better fit, then.

Based on this (place=isolated_dwelling), it appears that isolated dwellings are better suited for areas (when the area is known, which this is), but I'm open to further thoughts on it.

Good catch; it is fixed!

Got it fixed, thanks!

Yup, must have slipped when assigning route relation and hit the county boundary instead. Should be fixed.

You can use Overpass to scan for broken relations. Wireguy is also an active member who excels at ensuring relations are working (they've caught a few of my oopsies); you could ask them for advice as well on either relations or using Overpass (I haven't used it much myself).

Be careful when working with relations; you broke some.

This edit seems to be made in error. US Highways do not actually pass through Yellowstone (yes, it's weird); they terminate at the gate and resume on the other side. Also, hyphens are never used in ref tags. Please revert. Thank you!

I think I fixed it; let me know if that didn't work. There were some construction edits in that area recently so I'm not entirely sure what went wrong.

...Yep, I knew that. And forgot. Thanks for catching that!

Why did you divide this? It's not divided by a median. In addition, you left some knobs of roads and broke some relations. Please be more careful in the future.

Why did you revery these trunk roads to primary? under the new classification standards, trunks are supposed to form a complete network, avoiding spurs when possible.

The interchange with Homestead Expwy was not correctly done. The way you have done this, the trunk designation randomly stops, as opposed to the prior configuration where it led directly into the onramp. Having the junction between the secondary road and the trunk road occur at a bridge gap furthermore complicates the situation because it causes the secondary road visually to get priority.

In addition, turn lanes that are not divided from the main road (such as this case) should not be drawn separately but designated using tags. Otherwise it implies that there is a separate road.

You need to revert this edit. OSM standards do not allow 2 lane freeways to be marked as motorway. This was correctly labeled previously as a trunk road and expressway.

Just because it is in the NHS does not make it a trunk road. Please remember that OSM has its own set of standards. This results in a trunk spur, which should be avoided.

I see you've been doing a lot of much needed edits in Kansas. I encourage you to start discussions on #local_kansas on Slack and maybe even start the Kansas Highway Classification page on the wiki.