fix(lang/rust): links

Author: vados-cosmonic

component-model/src/language-support/creating-runnable-components/rust.md

@@ -2,13 +2,16 @@
 
 ## Exporting the `wasi:cli/run` interface
 
-Any reactor (library-like) component can *also* export the [`run` interface]wasi-cli-iface-run] inside [WASI CLI][wasi-cli],
+Any reactor (library-like) component can *also* export the [`run` interface][wasi-cli-iface-run] inside [WASI CLI][wasi-cli],
 and signal to ecosystem projects that it can be executed.
 
 > [!WARNING]
 > Reactor components can be reused, and while most platforms may *not* choose to reuse a component after `wasi:cli/run`
 > has been called, there is no guarantee that they will or will not.
 
+[wasi-cli-iface-run]: https://github.com/WebAssembly/wasi-cli/tree/main/wit/run.wit
+[wasi-cli]: https://github.com/WebAssembly/wasi-cli
+
 ### 1. Create a new Rust library project
 
 To build a simple component that exports `wasi:cli/run`, first create a new Rust project:

component-model/src/language-support/using-wit-resources/rust.md

@@ -1,6 +1,6 @@
 # Using WIT Resources (Rust)
 
-[Resources](../design/wit.md#resources) are handles to entities that live outside the component (i.e. in a host, or other component).
+[Resources](../../design/wit.md#resources) are handles to entities that live outside the component (i.e. in a host, or other component).
 
 ## An example stack-based Reverse Polish Notation (RPN) calculator
 
@@ -114,7 +114,7 @@ This completes the implementation of the calculator `engine` resource. Run `carg
 
 To use the calculator engine in another component, that component must import the resource.
 
-1. [Create a runnable component](../../creating-runnable-components/rust.md) as shown in previous sections.
+1. [Create a runnable component](../creating-runnable-components/rust.md) as shown in previous sections.
 
 2. Add a `wit/component.wit` to your project, and write a WIT world that imports the RPN calculator types:
 
@@ -158,7 +158,7 @@ To use the calculator engine in another component, that component must import th
 
 Building the component as is creates a WebAssembly component with an *unsatisfied import* -- namely the `docs:rpn/types` import.
 
-After building the component, it must be [composed with a `.wasm` component that implements the resource.](../composing-and-distributing/composing.md). After composition creates a component with no unsatisfied imports, the composed command component can be run with `wasmtime run`.
+After building the component, it must be [composed with a `.wasm` component that implements the resource.](../../composing-and-distributing/composing.md). After composition creates a component with no unsatisfied imports, the composed command component can be run with `wasmtime run`.
 
 Alternatively, a host that can provide the `docs:rpn/types` import (and related resource) can also be used to run the component
 in it's "incomplete" state (as the host will "complete" the componnt by providing the expected import).