Update docs of raytrace-parallel (#3026)

Author: lukaslihotzki

examples/raytrace-parallel/README.md

@@ -4,7 +4,7 @@
 online][compiled]
 
 [dox]: https://rustwasm.github.io/docs/wasm-bindgen/examples/raytrace.html
-[compiled]: https://rustwasm.github.io/wasm-bindgen/exbuild/raytrace-parallel/
+[compiled]: https://wasm-bindgen.netlify.app/exbuild/raytrace-parallel/
 
 You can build the example locally with:
 

guide/src/examples/raytrace.md

@@ -52,10 +52,11 @@ through `wasm-pack`, for example.
 
 ### Running the demo
 
-Currently it's required to use the `--target no-modules` flag with
-`wasm-bindgen` to run threaded code. This is because the WebAssembly file
+Currently it's required to use the `--target no-modules` or `--target web` flag
+with `wasm-bindgen` to run threaded code. This is because the WebAssembly file
 imports memory instead of exporting it, so we need to hook initialization of the
-wasm module at this time to provide the appropriate memory object.
+wasm module at this time to provide the appropriate memory object. This demo
+uses `--target no-modules`, because Firefox does not support modules in workers.
 
 With `--target no-modules` you'll be able to use `importScripts` inside of each
 web worker to import the shim JS generated by `wasm-bindgen` as well as calling
@@ -79,10 +80,10 @@ improvements to be made so if you have an idea please file an issue!
   synchronization with the main thread.
 
 * Setting up a threaded environment is a bit wonky and doesn't feel smooth
-  today. For example `--target no-modules` is required with `wasm-bindgen` and
-  very specific shims are required on both the main thread and worker threads.
-  These are possible to work with but are somewhat brittle since there's no
-  standard way to spin up web workers as wasm threads.
+  today. For example `--target bundler` is unsupported and very specific shims
+  are required on both the main thread and worker threads. These are possible to
+  work with but are somewhat brittle since there's no standard way to spin up
+  web workers as wasm threads.
 
 * There is no standard notion of a "thread". For example the standard library
   has no viable route to implement the `std::thread` module. As a consequence