proper docs and .version

rig/docs/notes/check.md

@@ -54,7 +54,7 @@ switch for the host part, so the standalone `rigdeps.sh detect` is short too.
 rig knows what a node costs (NODE_MB), not what a workload does, so the parts come from the
 overlay's rig.env: `MEMORY_BUDGET="name=MB ..."`, in the order listed; a 0 is left out, and an
 entry that is not `name=MB` is a `!` line. rig.env is sourced, so an overlay can size a part by
-its own knob (poc_rig's airflow follows its mode). When one part outweighs the rest together
+its own knob (an airflow sized by the mode the overlay runs it in). When one part outweighs the rest together
 (and is at least 1 GB), check names it as the first thing to switch off; `MEMORY_BUDGET_TIP`
 says how, in the overlay's words. No budget: one `?` row says where to add it.