@@ -44,9 +44,9 @@ as well as the text format for WebAssembly (`*.wat`):
44
44
wasmtime foo.wat
45
45
```
46
46
47
- #### Running "Command" Wasms
47
+ #### Running WebAssembly CLI programs
48
48
49
- WebAssembly modules or components can behave like a "command" which means
49
+ WebAssembly modules or components can behave like a CLI program which means
50
50
they're intended to look like a normal OS executable with a ` main ` function and
51
51
run once to completion. This is the default mode of running a wasm provided to
52
52
Wasmtime.
@@ -55,24 +55,24 @@ For core WebAssembly modules this means that the function exported as an empty
55
55
string, or the ` _start ` export, is invoked. For WebAssembly components this
56
56
means that the ` wasi:cli/run ` interface is executed.
57
57
58
- For both core modules and components CLI arguments are passed via WASI. Core
58
+ For both core modules and components, CLI arguments are passed via WASI. Core
59
59
modules receive arguments via WASIp1 APIs and components receive arguments via
60
- WASIp2 or later APIs. Arguments, flags, etc, are passed to the WebAssembly file
61
- after the file itself. For example:
60
+ WASIp2 or later APIs. Arguments, flags, etc. , are passed to the WebAssembly file
61
+ after the file itself. For example,
62
62
63
63
``` console
64
64
wasmtime foo.wasm --bar baz
65
65
```
66
66
67
67
Will pass ` ["foo.wasm", "--bar", "baz"] ` as the list of arguments to the module.
68
68
Note that flags for Wasmtime must be passed before the WebAssembly file, not
69
- afterwards. For example
69
+ afterwards. For example,
70
70
71
71
``` console
72
72
wasmtime foo.wasm --dir .
73
73
```
74
74
75
- will pass ` --dir . ` to the ` foo.wasm ` program, not Wasmtime. If you want to
75
+ Will pass ` --dir . ` to the ` foo.wasm ` program, not Wasmtime. If you want to
76
76
mount the current directory you instead need to invoke
77
77
78
78
``` console
0 commit comments