From 3c3bfaf0df5ac75ddd673778c4b64b3ac670aff3 Mon Sep 17 00:00:00 2001 From: Chris Barnes Date: Thu, 4 Oct 2018 11:29:51 -0400 Subject: [PATCH] Update README.md Fixed a quick typo in the readme [skip ci] --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c321e86c3..a60b456ae 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ The polyfill hosts the imported documents in the import link element. E.g. The polyfill fires the `HTMLImportsLoaded` event when imports are loaded, and exposes the `HTMLImports.whenReady` method. This api is necessary because unlike the native implementation, script elements do not force imports to resolve. Instead, users should wrap code in either an `HTMLImportsLoaded` handler or after load time in an `HTMLImports.whenReady(callback)` call. -The polyfill provides the `HMTLImports.importForElement()` method which can be used to retrieve the `` that imported an element. +The polyfill provides the `HTMLImports.importForElement()` method which can be used to retrieve the `` that imported an element. ## Caveats / Limitations @@ -26,7 +26,7 @@ The polyfill provides the `HMTLImports.importForElement()` method which can be u The polyfill appends the imported contents to the `` itself to leverage the native implementation of [Custom Elements](https://www.w3.org/TR/custom-elements), which expects scripts upgrading the `CustomElementRegistry` to be connected to the main document. -As a consequence, `.ownerDocument` will be the main document, while `.parentNode` of the imported children will be the `` itself. Consider using `HMTLImports.importForElement()` in these cases. e.g: +As a consequence, `.ownerDocument` will be the main document, while `.parentNode` of the imported children will be the `` itself. Consider using `HTMLImports.importForElement()` in these cases. e.g: ```javascript const ownerDoc = HTMLImports.importForElement(document.currentScript);