From e03b70f4aa6a05943b0394640a43b9a3b2031dfb Mon Sep 17 00:00:00 2001 From: Radu Matei Date: Sat, 9 Apr 2022 14:01:17 +0200 Subject: [PATCH] chore: address a few typos Signed-off-by: Radu Matei --- design/high-level/UseCases.md | 4 +--- design/mvp/Explainer.md | 2 +- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/design/high-level/UseCases.md b/design/high-level/UseCases.md index 608e6d06..a65e76c7 100644 --- a/design/high-level/UseCases.md +++ b/design/high-level/UseCases.md @@ -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 @@ -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 diff --git a/design/mvp/Explainer.md b/design/mvp/Explainer.md index 403c3657..422c6ae6 100644 --- a/design/mvp/Explainer.md +++ b/design/mvp/Explainer.md @@ -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).