aboutsummaryrefslogtreecommitdiff
path: root/TextFormat.md
diff options
context:
space:
mode:
authorChristophe de Dinechin <christophe@taodyne.com>2016-11-10 10:32:19 +0100
committertitzer <titzer@google.com>2016-11-10 10:32:19 +0100
commitaa8a5ae8f80e6023f6be03f5adbd91656b9def24 (patch)
treea0b90aa7a342b60014ede87515b495190b452525 /TextFormat.md
parente686a03efd88f124f99e166254780a59a82dd70d (diff)
downloadnanowasm-design-aa8a5ae8f80e6023f6be03f5adbd91656b9def24.tar.gz
Fix a typo and an error (#866)
* Fix typo on "semantics" * Fix encoding for 'end', which should be 0x0b and not 0x0f.
Diffstat (limited to 'TextFormat.md')
-rw-r--r--TextFormat.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/TextFormat.md b/TextFormat.md
index 4c27ce3..29d6880 100644
--- a/TextFormat.md
+++ b/TextFormat.md
@@ -9,7 +9,7 @@ modules.
# Linear bytecode
-WebAssembly function bodies encode bytecode instructions which have specified canonical opcode names. A linear presentation of these sequences of instructions allows a direct human-readable order-preserving presentation of the binary format. This format is suitable for opcode by opcode inspection of a WebAssembly program and can readily be related to the [sematics](Semantics.md) of the format.
+WebAssembly function bodies encode bytecode instructions which have specified canonical opcode names. A linear presentation of these sequences of instructions allows a direct human-readable order-preserving presentation of the binary format. This format is suitable for opcode by opcode inspection of a WebAssembly program and can readily be related to the [semantics](Semantics.md) of the format.
Here is an example function illustrated in C++, binary, and text (linear
assembly bytecode):