Please don't delete existing valid roads and redraw them anew. Doing so is against OSM good practice. Please just modify the existing roads by adjusting their geometry or changing their tags. osm.wiki/Keep_the_history For the parking aisle you deleted, you could've just retagged it to a service road by removing the service=parking_aisle tag (In the iD editor, at the bottom of the left-hand sidebar of the selected feature underneath "Tags", you can click on the trash can icon to the right of the tag, and it will remove the tag from the selected feature.): way/943071435/history

To retag a road or change a road's classification in iD editor, in the left-hand sidebar of the selected feature, click on the road's current feature type at the top of the sidebar or click on the back button at the top left of the sidebar. Then a list of different feature types will show.
Click on the "Major Roads" or "Minor Roads" folder, and a list of different road types will appear underneath the folders. You can also click on the search bar at the top of the sidebar and type the road type that you want to change the selected road to.
Click on the road type that you want to change the selected road to, and it will change the selected road's classification.

You should visit the FacilMap link of this changeset to see which road you deleted and redrew in this changeset: https://facilmap.org/#q=changeset%20161888498

Just a tip, when you find a single node for an object and want to draw the outline of the building or the campus, it is good practice to keep the node (without its tags) as one of the nodes in the outline (e.g. as a corner of the building or the campus entrance). This preserves the history of the information in the "old" node, which is easy to find when somebody inspects such an object. To do this in iD, draw the area with the node as one of the corners, copy the tags from the node and delete all its tags, then paste the tags on the area outline (In iD, you can also hold down the "Shift" key on your keyboard and select the area and the node, and press "C" to merge the node data with the area).
osm.wiki/Keep_the_history#Editing_techniques

For the church node you deleted in this changeset (node/356573430/history), you could've moved the node onto one of the nodes of the church building outline you drew (way/1355593079/history), and copied the node's tags and pasted them on the building outline.

You incorrectly spelled "Belview" in this changeset's comment. "Belview has one "l", not two l's.

Looking at your changeset comment, it's "NS" for Norfolk Southern (the railroad company), not "N&S". It's the former Virginian Railway line (the NS Whitethorne District), not "Virginia Line". I know this since I'm a train enthusiast that has been railfanning on the NS Christiansburg and Whitethorne Districts.

Please do not remove map elements you don't need or don't like. It looks like you adjusted some existing roads in this changeset, but merged a few roads into one road. Inaccurate mapping is not forbidden, but you certainly should not work the other way and remove details that someone else added. It is known that not everything is always needed by everyone, but you must not remove map elements just because you do not need it or you think it is stupid.
osm.wiki/Good_practice#Don't_remove_objects_that_you_don't_need_or_like

You also incorrectly spelled "Belview" in this changeset's comment. "Belview has one "l", not two l's.

You can visit this FacilMap link of this changeset to see which elements you added, modified, or deleted: https://facilmap.org/#q=changeset%20161332512

Do not delete existing map elements and redraw them anew. Doing so is against OSM good practice. For the parking areas you deleted in this changeset, you could've just modified their geometry by adding or moving nodes on them instead of deleting the parking areas and redrawing them anew.
way/1108008942/history
way/1108008943/history

Please take a few steps to help preserve the history on OSM.
osm.wiki/Keep_the_history

You can visit the FacilMap link of this changeset to see which elements you created, which elements you modified, and which elements you deleted: https://facilmap.org/#q=changeset%20161330743

Please don't just auto-accept the suggested fixes by the iD editor. You added a ford to where there is not actually a ford: node/13370313749

And since you're part of an organized editing group, it is important that you follow the Organized Editing Guidelines. osm.wiki/Organised_Editing/Guidelines
The Organized Editing Guidelines are found here: https://osmfoundation.org/wiki/Organised_Editing_Guidelines, and under "Possible actions on problematic edits", they state that:

"Problematic edits may be reverted. In cases of severe or repeated problems, individuals and organisations may be banned from editing OpenStreetMap."

However, many, if not all of your edits, have been problematic by damaging or deleting valid map data, retagging roads within school zones and residential areas to unclassified roads when they don't need to be, and adding non-existent roads or other features. Please do not damage or delete valid map data, or add non-existent features on OSM. Please note that if you continue those problematic map edits, then you could be blocked from editing OSM.

Please take care not to damage valid map data by changing valid administrative or suburb boundaries into roads, and only map features that actually exist on the ground.

Hey TransAct-AS, I see that you deleted a valid sidewalk: way/1017884441. I can clearly see the sidewalk in aerial imagery. Please do not delete existing valid map data. It is considered vandalism and can get you banned from OSM. What is the source for the deletion of this sidewalk?

Please map and align roads to those in aerial imagery. The manner in which you mapped this road is not correct because it is not aligned with that in aerial imagery: way/1445765156 (This road would be better tagged as highway=service + service=parking_aisle!)

Please do not damage valid map data by changing valid administrative/municipal boundaries into roads. This is not acceptable, and it damages the map. Also, please don't glue roads to administrative boundaries.

Please don't just auto-accept the suggested fixes by the iD editor. You added a bridge to where there is not actually a bridge: way/1452341528

Those roads would be better tagged as highway=residential instead of unclassified roads since they're within a residential area.

Also, you added a bridge to where there is not actually a bridge. Just a cycle path crossing on the road. way/1452341528
Please do not add non-existent features to OSM. Please only add features that actually exist on the ground.

Those roads within this newly constructed residential area would be better tagged as highway=residential rather than unclassified roads since they provide access to homes.

Please see my comment in changeset/174860871

Why did you change this road to an unclassified road. Another mapper first mapped this road as a service road, then you changed it to a residential road and now an unclassified road. way/1450336042/history
Can you explain the reason for changing this road to an unclassified road? Thanks.

Can you explain why you have been changing valid service roads and driveways around schools to unclassified roads? I don't think those roads serving this school should be tagged as unclassified roads. Those would probably be better tagged as highway=service.

Are you trying to tag for the router by changing valid service roads and driveways around schools to unclassified roads? If so, then please note that tagging for the router is against OSM good practice. Do not use inaccurate tags or distort data associated with map features to influence routing navigation towards your preferred router. Routing software is consistently improving. If you tag for the router, then it can mislead routers into completely avoiding those roads or paths, or potentially allowing other vehicle categories. Consider trying an alternative option or reporting any issues or improvement suggestions to the different routing projects. Per the "Don't map for the router" section on the OSM Wiki article on good practice, it states:

"Do not use inaccurate tags or distort data to influence routing navigation to your preferences. Familiarize yourself with best practices instead. Since routers are consistently improving, consider trying an alternative option or reporting any issues or improvement suggestions to the different routing projects."
osm.wiki/Good_practice#Don't_map_for_the_router

osm.wiki/Tagging_for_the_router

Please make sure to provide sources for street name changes like this. It looks like you corrected some street names around here. Make sure to provide sources for street name changes or corrections in your changesets.

I did not add this in my previous comments:

This changeset also added a ford to where there is not actually a ford, just a bridge crossing a stream: node/13342453663
A ford is a small part of a highway where a waterway runs over it. It is distinct from a bridge which goes over the waterway, or a culvert where the waterway goes under the highway.
ford=*

I also retagged the existing abandoned railway (because it was retagged from highway=road to an abandoned railway after you mapped the duplicate cycleway) to a cyclepath in a follow-up changeset: changeset/176929593