aboutsummaryrefslogtreecommitdiff
path: root/BinaryEncoding.md
diff options
context:
space:
mode:
authorDan Gohman <sunfish@mozilla.com>2015-06-15 10:13:35 -0800
committerDan Gohman <sunfish@mozilla.com>2015-06-15 09:25:45 -0700
commitef6799f98620b327e7668075dd709f532e60ace2 (patch)
tree7ad4d9c434a828a1189e4e85db370cd39821d3f0 /BinaryEncoding.md
parent18a5288b99a812b9237f426c1194876afa2362d4 (diff)
downloadnanowasm-design-ef6799f98620b327e7668075dd709f532e60ace2.tar.gz
Add trailing slashes to URLs that want it.
Diffstat (limited to 'BinaryEncoding.md')
-rw-r--r--BinaryEncoding.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/BinaryEncoding.md b/BinaryEncoding.md
index 0635a20..9788abf 100644
--- a/BinaryEncoding.md
+++ b/BinaryEncoding.md
@@ -108,7 +108,7 @@ F1 and F2 and vendor V1 implements F1, assigning the next logical opcode indices
opcodes, and V2 implements F2, assigning the same next logical opcode indices to F2's new opcodes
and now a single binary has ambiguous semantics if it tries to use either F1 or F2. This type of
non-linear feature addition is commonplace in JS and Web APIs and is guarded against by
-having unique names for unique features (and associated [conventions](https://hsivonen.fi/vendor-prefixes)).
+having unique names for unique features (and associated [conventions](https://hsivonen.fi/vendor-prefixes/)).
The current proposal is to maintain both the efficiency of indices in the [serialized AST](BinaryEncoding.md#serialized-ast) and the established
conflict-avoidance practices surrounding string names: