You changed the route of the A516 from trunk to trunk_link, I've put it back to trunk, it's not a connection between A roads, it is the A road.

No, these *are* the A516, reverted.

It was necessary to reverse all your changes due to the damage caused. All the ways are already mapped. To add a cycle route, you would need to create a 'route relation' which you can name for example 'Ambon-Damgan' and select each of the existing ways that make up that route.
You damaged the D140 road, a track, an admin boundary, power lines and created multiple duplicate cycle ways, and a way which seems to be fiction. So everything is put back as it was.
[Google translate follows]
Il a été nécessaire d'annuler toutes vos modifications en raison des dommages causés. Tous les chemins sont déjà tracés. Pour ajouter une 'route' cyclable, vous devrez créer une « 'route' relation » que vous pourrez nommer par exemple « Ambon-Damgan » et sélectionner chacune des voies existantes qui composent cette route.
Vous avez endommagé la route D140, une piste, une limite administrative, des lignes électriques et créé plusieurs pistes cyclables en double, et une voie qui semble être une fiction. Donc tout est remis comme avant.

@ExoMal, you can (and should) achieve an order of magnitude better alignment accuracy using the UK OSM Cadastral parcels layer. Align the imagery to that (ignoring OSM mapped features) eg using low garden walls and pavement edges. Then align OSM data to that aligned imagery. This avoids repeated realignment to each new (often poorly aligned) version of imagery, and disturbing other users' good mapping

No problem. Yes, node or area are both ok for amenity, shop etc. The only information you didn't have is that "area" is just a way that is closed into a loop to form the boundary, and the only object types (that can have key=value tags) stored in OSM are really node, way and relation. So landuse areas, buildings etc are just stored as ways, although note you can also use relations (containing an outer and inner way loop(s)) to make areas with holes.

Welcome to OSM. It is entirely normal for a business or (in this case) amenity that occupies the whole of a building to have the tags on that building outline.
See amenity=pub
If the application you are using does not handle that, it is a fault of that application not the map. I have undeleted the building outline you wrongly removed in this changeset; do not delete valid mapping and degrade the map for your own benefit. (I have left the pub details on your node for now)

And the signposted permissive path?

Has the bridge at the upper lock been destroyed? Has the mapped permissive path been permanently closed?

The absence of a paved sidewalk does not make it illegal to walk along a road in the UK. In this case there is a verge; even if not provided it would be entirely legal to walk along the road. Your foot=no removed.

Welcome to OSM and thanks for adding your London showroom details, although your edit didn't seem to go as intended - you ended up with the London information on the Swansea location and also on a residential area around the London showroom.
I've reset the Swansea information and added a node in London which you can check/update as necessary:
node/4989144188/history
node/11042617097/history
Cebderby (Clive)

I've undeleted way/659403213/history
which carries a public footpath, wrongly deleted in this changeset.

Hi Phil,
There's a footpath-sized gap between the property boundaries on the Cadastral layer, but I've deleted this (non) way now, thanks.
Cebderby (Clive)

Reverted. This line was not a highway (hence highway=no) but the definitive line of the public footpath which the actual diverges from. It's correctly tagged and correctly exists.

Thanks for identifying this error - seems the road junction node had been wrongly merged onto the bridleway gate node in ch. 93862566. Unfortunately by deleting the node (not just the gate tag) you shortened both the bridleway and Church Lane. All is fixed up with the ways reconnected and a gate back in place where it was originally on the bridleway.

I've reverted this as the barriers with traffic lights that you deleted exist. Routing is fine (as it was) in all 3 routers on the OSM website and in OSMAnd, but I have now added access=yes to the barrier nodes in case this helps whatever you use.
Please do not damage the map to suit a specific map renderer or router that may be buggy.

Reverted, is public bridleway as was correctly tagged.
https://osm.mathmos.net/prow/progress/dorset/-/winterborne-houghton/

Hi Jez,
Thanks for your message. The widespread use of junction=circular seems to be fairly recent, or maybe the OSM wiki definition has shifted (as they do) to make them much more common.
If you compare
junction=circular
and
junction=roundabout
I think junction=circular, oneway=yes is correct here due to the (at least one, in this case two) traffic light controlled entry points on the N side, with junction=roundabout now only applying to 'normal' roundabouts with no right of way restrictions to the inner loop. I think most common routers present them the same (eg OSMAnd will still say take the Nth exit at the roundabout) either way.
Cebderby (Clive)

You've not succeeded in setting either building=retail or shop=mall as it was.
First changeset:
https://overpass-api.de/achavi/?changeset=138059109
This changeset:
https://overpass-api.de/achavi/?changeset=138064363
Someone (and it should be you) needs to go back through your changesets - you can use the above links with the relevant changeset numbers from your list of edits
@joshwalton07/history
and carefully review.
Also, note that building:levels should be the actual number of levels of the building, not just an arbitrary high value for a tall building. Use height= with your best estimate of building height in metres. eg if it's as tall as a normal 4 storey building but only has 2 tall floors, set building:levels=2 and height=12 (estimate 3 or 3.5 m per floor for an ordinary residential building)

Sorry, meant set building=yes back to building=church

Can you re-add religion=christian and set building=yes that you also removed.
https://overpass-api.de/achavi/?changeset=138054013