diff options
author | Jason Cooke | 2019-07-05 22:00:10 +1200 |
---|---|---|
committer | GitHub | 2019-07-05 22:00:10 +1200 |
commit | 1bacb27072ecd5b057ee68f29df6cad3ee5f76ce (patch) | |
tree | 59404d1633ef46ec19510883eabfae3df0f29685 | |
parent | 33bed47daca3f08c396215415e6ece005970734a (diff) |
docs: fix typo
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1237,7 +1237,7 @@ Then: Plugins should register themselves with reveal.js by calling `Reveal.registerPlugin( 'myPluginID', MyPlugin )`. Registered plugin instances can optionally expose an "init" function that reveal.js will call to initialize them. -When reveal.js is booted up via `Reveal.initialize()`, it will go through all registered plugins and invoke their "init" methods. If the "init" method returns a Promise, reveal.js will wait for that promise to be fullfilled before finshing the startup sequence and firing the [ready](#ready-event) event. Here's an example of a plugin that does some asynchronous work before reveal.js can proceed: +When reveal.js is booted up via `Reveal.initialize()`, it will go through all registered plugins and invoke their "init" methods. If the "init" method returns a Promise, reveal.js will wait for that promise to be fulfilled before finshing the startup sequence and firing the [ready](#ready-event) event. Here's an example of a plugin that does some asynchronous work before reveal.js can proceed: ```javascript let MyPlugin = { |