Very good point, I'll fix that for next year's survey. Fortunately for people working with WebAssembly those two terms are synonymous, so this will not effect the results.
Btw, while you're here, another suggestion: Perhaps include Node.js as a runtime option? It's not a pure wasm VM, obviously, but it may be a common way to run wasm on the server simply because npm packages can include wasm. (OTOH, users of such packages might not even know they're using wasm...)