Please improve docs for worker version key and overrides

[Meai]

Existing documentation URL(s)

https://developers.cloudflare.com/workers/configuration/versions-and-deployments/gradual-deployments/

What changes are you suggesting?

1. To me Cloudflare-Workers-Version-Key and Cloudflare-Workers-Version-Override both sound like they can change which worker will respond to a request. I don't know what the difference is, I can't tell how it influences the "affinity" or how it would somehow influence later requests just because I sent one request with a key. Does it mean per keep-alive connection or curl session somehow? I don't understand how it would achieve affinity.
2. I just spent - it must have been almost 1.5h - to finally notice this seemingly innocent sentence A version override will only be applied if the specified version is in the current deployment and realizing that it carries a lot of weight. Because it's quite unintuitive that I'm saving a worker version and it is clearly deployed in some form because the preview url exists and it is running.. and yet in this context it doesn't count as deployed at all. It needs me to do a special "gradual" version deployment where I can then set one of the versions to 0% and the other remains at 100% and now they both count as deployed and the version with 0% can still receive requests via header override.
3. Please also link to wherever the syntax was for doing this gradual deployment via wrangler cli, there was some kind of special syntax that I found somewhere but I can't find it anymore right now.
4. Really sad that this only allows for version overrides for two versions. I want to target any of my deployed preview url versions via override. I need a header based override so that it works via service binding.

Additional information

No response