fix: links, markdown

Author: vados-cosmonic

component-model/src/language-support/rust.md

@@ -112,7 +112,7 @@ cargo add wit-bindgen
 > The command above should be run from inside the `adder` directory that was created by
 > `cargo new` so as to be sure to add `wit-bindgen` to the dependencies of the right project. Alternatively, you can directly add `wit-bindgen` to the dependencies section of the `Cargo.toml`.
 >
-> While it is also possible to use `wit-bindgen` as a binary via the [`wit-bindgen-cli`][wit-bindgen-cli]
+> While it is also possible to use `wit-bindgen` as a binary via the [`wit-bindgen-cli`][crates-wit-bindgen-cli]
 > crate, but here we will focus on a code-first binding build approach.
 
 Once you have `wit-bindgen` as a part of your Rust project (i.e. in `Cargo.toml`), we can use it to generate Rust code bindings for our WIT interface. Update your `src/lib.rs` file to look like the following:
@@ -132,7 +132,7 @@ mod bindings {
 }
 ```
 
-Here we create a module called `bindings` that contains the code output by the [`wit_bindgen::generate` macro][rustdoc-wit-bingen-generate].
+Here we create a module called `bindings` that contains the code output by the [`wit_bindgen::generate` macro][rustdoc-wit-bindgen-generate].
 Various `struct`s, `interface`s, `enum`s and more might be generated by `wit_bindgen`, so it's often desirable to sequester those new
 types to a module that can be referred to later.
 

component-model/src/tutorial.md

@@ -150,7 +150,7 @@ docs = { registry = "docs",  metadata = { preferredProtocol = "oci", "oci" = {re
 > [!NOTE]
 > We have published the [`docs:adder` WIT package](https://github.com/orgs/bytecodealliance/packages/container/package/docs%2Fadder) to GHCR ahead of time, so it is easy to find/access via the configuration above.
 >
-> To make your own custom WITs available, please use the [`wkg publish`](../../composing-and-distributing/distributing.md#distributing-wit-and-components-by-package-name-with-wkg-publish) command.
+> To make your own custom WITs available, please use the [`wkg publish`](./composing-and-distributing/distributing.md#distributing-wit-and-components-by-package-name-with-wkg-publish) command.
 
 With the project scaffolded, now we must actually *implement* a command line application that:
 
@@ -163,6 +163,7 @@ For reference, see the [completed code listing](https://github.com/bytecodeallia
 [wkg]: https://github.com/bytecodealliance/wasm-pkg-tools/tree/main/crates/wkg
 [wasm-pkg-tools]: https://github.com/bytecodealliance/wasm-pkg-tools/tree/main
 [wiki-entrypoint]: https://en.wikipedia.org/wiki/Entry_point
+[cargo]: https://doc.rust-lang.org/cargo
 
 ## Composing the calculator
 
@@ -206,3 +207,5 @@ expanded enum.
 Another extension of this tutorial could be to remove the `op` enum and instead modify
 `eval-expression` to take in a string that can then be parsed to determine which operator component
 to call. Maybe this parser is a component of its own?!
+
+[!NOTE]: #