From 784d286e98bdc6bf30f8fa12c6038d2f3fcb6f80 Mon Sep 17 00:00:00 2001
From: Daniel Freedman <dfreedm@google.com>
Date: Fri, 21 Apr 2017 18:15:37 -0700
Subject: [PATCH] update README with webComponentsReady property

---
 README.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index ad36c46..54807fb 100644
--- a/README.md
+++ b/README.md
@@ -35,7 +35,11 @@ Alternatively, this repo also comes with `webcomponents-loader.js`, a client-sid
 loader that dynamically loads the minimum polyfill bundle, using feature detection.
 Note that because the bundle will be loaded asynchronously, you should wait for the `WebComponentsReady` before you can safely assume that all the polyfills have
 loaded and are ready to be used (i.e. if you want to dynamically load other custom
-elements, etc.). Here's an example:
+elements, etc.).
+
+Additionally, you can check the `webComponentsReady` property on the `webcomponents-loader.js` script to determine if the `WebComponentsReady` event has been fired.
+
+Here's an example:
 
 ```html
 <!-- Load polyfills; note that "loader" will load these async -->
@@ -68,7 +72,7 @@ To work around this, load `custom-elements-es5-adapter.js` before declaring new
 **The adapter must NOT be compiled.**
 
 ```html
-<!-- Load Custom Elements es5 adapter --> 
+<!-- Load Custom Elements es5 adapter -->
 <script src="bower_components/webcomponentsjs/custom-elements-es5-adapter.js"></script>
 <!-- Load polyfills; note that "loader" will load these async -->
 <script src="bower_components/webcomponentsjs/webcomponents-loader.js"></script>