Skip to content

chore: address a few typos #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2022
Merged

chore: address a few typos #20

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions design/high-level/UseCases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ sandboxing technology):
#### Invoking component exports from the host

Once a host chooses to embed wasm (for one of the preceding reasons), the first
design choice is how host executes the wasm code. The core wasm [start function]
design choice is how the host executes the wasm code. The core wasm [start function]
is sometimes used for this purpose, however the lack of parameters or results
miss out on several use cases listed below, which suggest the use of exported
wasm functions with typed signatures instead. However, there are a number of
Expand Down Expand Up @@ -325,8 +325,6 @@ to call imports, which could break other components' single-threaded assumptions
the imported function to have been explicitly `shared` and thus callable from
any `fork`ed thread.



[RLBox]: https://plsyssec.github.io/rlbox_sandboxing_api/sphinx/
[Principle of Least Authority]: https://en.wikipedia.org/wiki/Principle_of_least_privilege
[Modular Programming]: https://en.wikipedia.org/wiki/Modular_programming
Expand Down
2 changes: 1 addition & 1 deletion design/mvp/Explainer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -398,7 +398,7 @@ appear syntactically within a `(module ...)` S-expression, there is never a
need to syntactically distinguish `functype` from `core:functype` in the text
format: the context dictates which one a `(func ...)` S-expression parses into.

A `valuetype` describes a single `intertype` value this is to be consumed
A `valuetype` describes a single `intertype` value that is to be consumed
exactly once during component instantiation. How this happens is described
below along with [`start` definitions](#start-definitions).

Expand Down