docs: fix typos in documentation

Fix various typos found across documentation files:
- CONTRIBUTING.md: "regenate" → "regenerate"
- README.md: "form your local" → "from your local"
- guide/src/assets/index.md: "avalid" → "a valid", "an may" → "and may"
- guide/src/advanced/javascript_interop.md: "wasm-bingen" → "wasm-bindgen"

Author: ursisterbtw

CONTRIBUTING.md

@@ -7,7 +7,7 @@ Just a few simple items to keep in mind as you hack.
 
 - Pull request early and often. This helps to let others know what you are working on. **Please use GitHub's Draft PR mechanism** if your PR is not yet ready for review.
 - Use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), a changelog will automatically be created from such commits
-- When making changes to the configuration, be sure to regenate the schema. This can be done by running:
+- When making changes to the configuration, be sure to regenerate the schema. This can be done by running:
 
   ```shell
   cargo run -- config generate-schema schemas/config.json

README.md

@@ -27,7 +27,7 @@ Head on over to the [Trunk website](https://trunkrs.dev), everything you need is
   - `cargo binstall trunk` (installing a pre-compiled binary using [cargo-binstall](https://github.com/cargo-bins/cargo-binstall))
   - `cargo install trunk --locked` (compile your own binary from crates.io)
   - `cargo install --git https://github.com/trunk-rs/trunk trunk` (compile your own binary from the most recent git commit)
-  - `cargo install --path . trunk` (compile your own binary form your local source)
+  - `cargo install --path . trunk` (compile your own binary from your local source)
   - `brew install trunk` (installing from [Homebrew](https://brew.sh/))
   - `nix-shell -p trunk` (installing from [nix packages](https://nixos.org/))
 - [App Setup](https://trunkrs.dev//#app-setup)

guide/src/advanced/javascript_interop.md

@@ -3,7 +3,7 @@
 Trunk will create the necessary JavaScript code to bootstrap and run the WebAssembly based application. It will also
 include all JavaScript snippets generated by `wasm-bindgen` for interfacing with JavaScript functionality.
 
-By default, functions exported from Rust, using `wasm-bingen`, can be accessed in the JavaScript code through the global
+By default, functions exported from Rust, using `wasm-bindgen`, can be accessed in the JavaScript code through the global
 variable `window.wasmBindings`. This behavior can be disabled, and the name can be customized. For more information
 see the [`rust` asset type](../assets/index.md#rust).
 

guide/src/assets/index.md

@@ -112,7 +112,7 @@ Classic script assets processed by Trunk must follow these three rules:
 
 ```admonish attention
 A *valid* HTML `script` tag always has an end tag (like `<script></script>`). A self-closing script tag
-(like `<script />`) is **not** avalid HTML script tag and will trigger a warning an may create a non-working HTML file.
+(like `<script />`) is **not** a valid HTML script tag and will trigger a warning and may create a non-working HTML file.
 ```
 
 This will typically look like: `<script data-trunk src="{path}" ..other options here..></script>`. All `<script data-trunk ...></script>` HTML elements will be replaced with the output HTML of the associated pipeline.