aboutsummaryrefslogtreecommitdiff
path: root/DynamicLinking.md
diff options
context:
space:
mode:
authorJF Bastien <github@jfbastien.com>2016-03-15 11:13:45 -0700
committerJF Bastien <github@jfbastien.com>2016-03-15 11:13:45 -0700
commitd48ad63b0ca2a2e75b006260f4fd15bf5171e00a (patch)
tree2b5d3be5317c476ef5a6dd060dd0e89750452641 /DynamicLinking.md
parent21c6c37f01c69e5c0e49ec7cb66489fffca1a1fb (diff)
downloadnanowasm-design-d48ad63b0ca2a2e75b006260f4fd15bf5171e00a.tar.gz
Update DynamicLinking.md
Diffstat (limited to 'DynamicLinking.md')
-rw-r--r--DynamicLinking.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/DynamicLinking.md b/DynamicLinking.md
index 09a0a89..77983f3 100644
--- a/DynamicLinking.md
+++ b/DynamicLinking.md
@@ -4,7 +4,7 @@ Dynamic loading of code is in [the MVP](MVP.md) in the form of
[modules](Modules.md), but all loaded modules have their own separate
[linear memory](AstSemantics.md#linear-memory) by default and cannot share
[function pointers](AstSemantics.md#calls). Limited collaboration between
-modules is possible im the MVP by having two modules share the same linear
+modules is possible in the MVP by having two modules share the same linear
memory and invoke each other through the embedder.
True dynamic linking will allow developers to share memory *and* function