aboutsummaryrefslogtreecommitdiff
path: root/FAQ.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 /FAQ.md
parent18a5288b99a812b9237f426c1194876afa2362d4 (diff)
downloadnanowasm-design-ef6799f98620b327e7668075dd709f532e60ace2.tar.gz
Add trailing slashes to URLs that want it.
Diffstat (limited to 'FAQ.md')
-rw-r--r--FAQ.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/FAQ.md b/FAQ.md
index 8207fd1..28e4b69 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -36,7 +36,7 @@ memory usage is basically the size of the input plus the size of the decoded tex
Additionally, there are two further improvements that can be made in the real polyfill:
1. Decode while downloading using either chunked files, HTTP `Range` requests or (eventually)
- the [Stream API](https://www.w3.org/TR/streams-api).
+ the [Stream API](https://www.w3.org/TR/streams-api/).
2. Include optional better-than-`gzip` compression in the polyfill. For example, the
[lzham](https://github.com/richgel999/lzham_codec) library shows an *additional* 24%
improvement over the above "`gzip` binary" figures while maintaining high decode rates.
@@ -83,7 +83,7 @@ The [WebAssembly Community Group][] would be delighted to collaborate with more
compiler vendors, take their input into consideration in WebAssembly itself, and
work with them on ABI matters.
- [WebAssembly Community Group]: https://www.w3.org/community/webassembly
+ [WebAssembly Community Group]: https://www.w3.org/community/webassembly/
## Will WebAssembly support View Source on the Web?