Check bundlers chapter

Author: petervidos

docs/content/tutorial/0-intro.md

@@ -48,26 +48,20 @@ chart.initializing.then(
 )
 ```
 
-### Working with Bundlers, changing the location of the WASM module
+### Working with bundlers & frameworks
 
 The published Vizzu package contains a Javascript (*vizzu.min.js*) and a 
-WebAssembly (*cvizzu.wasm*) module. By default, the Javascript module tries to
-load the wasm module from the same path, it was imported from. 
+WebAssembly (*cvizzu.wasm*) module. By default, the Javascript module tries to load the wasm module from the same path it was imported from. 
 
-This behaviour won't work well with bundlers, if they move the wasm file to a 
-different folder. To handle this case, the location of the wasm module can be
-set for the library.
+This behavior won't work with bundlers if they move the wasm file to a different folder. To handle this issue, you can manually set the wasm module's location.
 
 ```Javascript { "run": false }
 Vizzu.options({ wasmUrl: "/path/to/cvizzu.wasm" })
 ```
 
-> Note: this should be set before the Vizzu constructor called, since it will
-> load the wasm module.
+> Note: you should set this path before the Vizzu constructor is called because it loads the wasm module.
 
-Different Bundlers will need additional bundler specific settings to recognize 
-the wasm file as dependency and to handle it correctly. For setting up Vizzu 
-with a specific bundler or framework, see the corresponding howto/example below:
+Different bundlers will need additional, specific settings to recognize the wasm file as a dependency and handle it correctly. For setting up Vizzu with a specific bundler or framework, check the corresponding how-to/example below:
 
 - Webpack: https://github.com/vizzuhq/vizzu-webpack-demo
 - React: https://vizzuhq.github.io/vizzu-react-example/