diff options
| author | Hakim El Hattab | 2019-07-08 10:01:55 +0200 |
|---|---|---|
| committer | GitHub | 2019-07-08 10:01:55 +0200 |
| commit | cf027f21c6db0c1766906063cb0f7ef14aba782a (patch) | |
| tree | bca63844d3a0c4e3c92da1d1c13541008c2cc689 | |
| parent | bd3758a4df0cef60c984551ad413df7a90862b2b (diff) | |
| parent | 1bacb27072ecd5b057ee68f29df6cad3ee5f76ce (diff) | |
Merge pull request #2451 from Jason-Cooke/patch-1
docs: fix typo
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1281,7 +1281,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 = { |