From c69e11aa289bf75e0e94b5c3586b2465639f297f Mon Sep 17 00:00:00 2001 From: ojan Date: Wed, 3 Jan 2018 16:40:04 -0800 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3b7962e..7b68434 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ Finally, there is a question as to whether we need explicit import at all. We co # Benefits By implementing as unprivileged Javascript, we are forced to identify and ship the appropriate low-level primitives needed to build the high-level feature. This gives web developers the tools they need to build their own versions and it allows us to experiment with the API design as a pure JS library before shipping. -Using modules means that features are explicitly imported, so the global namespace isn't poluted and sites only pay runtime costs for the features they use. +Using modules means that features are explicitly imported, so the global namespace isn't polluted and sites only pay runtime costs for the features they use. Implementing in Javascript also provides a clean implementation boundary. Changing part of the Javascript implementation can't create thorny bugs throughout the renderer.