From 55f72332514d98a68868d13d4f59aae55a12d3f1 Mon Sep 17 00:00:00 2001 From: Juha Lindfors Date: Wed, 5 Apr 2017 00:03:53 +0800 Subject: Typo: implementatin -> implementation (#1031) --- BinaryEncoding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'BinaryEncoding.md') diff --git a/BinaryEncoding.md b/BinaryEncoding.md index f131551..cf18b84 100644 --- a/BinaryEncoding.md +++ b/BinaryEncoding.md @@ -205,7 +205,7 @@ Custom sections are intended to be used for debugging information, future evolut If a WebAssembly implementation interprets the payload of any custom section during module validation or compilation, errors in that payload must not invalidate the module. -Known sections from the list below may not appear out of order, while custom sections may be interspersed before, between, as well as after any of the elements of the list, in any order. Certain custom sections may have their own ordering and cardinality requirements. For example, the [Name section](#name-section) is expected to appear at most once, immediately after the Data section. Violation of such requirements may at most cause an implementatin to ignore the section, while not invalidating the module. +Known sections from the list below may not appear out of order, while custom sections may be interspersed before, between, as well as after any of the elements of the list, in any order. Certain custom sections may have their own ordering and cardinality requirements. For example, the [Name section](#name-section) is expected to appear at most once, immediately after the Data section. Violation of such requirements may at most cause an implementation to ignore the section, while not invalidating the module. The content of each section is encoded in its `payload_data`. -- cgit v1.2.3