Arvados

Tom Clegg wrote:

preemptable → preemptible (and nonpreemptable → non-preemptible / regular / normal (GCE) / on-demand (AWS))

Fixed.

I think it's worth picking one term ("preemptible" or "spot") and sticking to it, only mentioning the other one as a synonym once early on, rather than using them interchangeably throughout. Probably "preemptible" since it's more generic and that's how it appears in our configs/logs.

Reworked the text a bit to use "preemptible" when talking about the general Arvados feature and "spot" when talking about AWS specifically.

Nit: I think it just adds information noise to use the term Crunch here -- maybe "how to set up crunch to take advantage" could just be "how to set up Arvados to take advantage"? If we do stick with crunch it seems like it should be capitalized for readability.

Too many words. Cut the sentence down to just "how to enable preemptible instances".

I notice we're referring to node manager as "legacy" even though arvados-dispatch-cloud still has an "experimental" warning -- but #13908 is on the map for 1.5, so I added #15775 and #15776 as blockers for that to make sure we bring the a-d-c/nodemanager pages up to speed with this one.

Sounds good to me.