Minor tidy-ups.

ntoll · ntoll · commit 11736d0c84ae · 2022-10-19T12:29:44.000+01:00
diff --git a/README.md b/README.md
@@ -105,16 +105,16 @@ The story of PyScript's execution is roughly as follows:
      plugin registered a `py-plugin-registered` event is dispatched, containing
      the (potentially changed) `config`, and a reference to the newly registered
      plugin.
-3. When `py-runtime-loaded` is dispatched the `config` is frozen and two things
-   happen:
+3. When `py-runtime-loaded` is dispatched two things happen:
    * The runtime is instantiated / started. Once complete the `py-runtime-ready`
      event is dispatched.
-   * All registered plugins have their `start` function called. 
+   * All registered plugins have their `start` function called and a
+     `py-plugin-started` event is dispatched for each plugin.
 4. When the `py-runtime-ready` event is dispatched all plugins have their
    `onRuntimeReady` function called with the `config` and `runtime` objects.
 5. Any plugins registered after the runtime is ready immediately have their
    `configure`, `start` and `onRuntimeReady` functions called, with the
-   `py-plugin-registered` event being dispatched.
+   `py-plugin-registered` and `py-plugin-started` events being dispatched.
 
 That's it!
 
@@ -227,7 +227,7 @@ Then in your HTML file:
 ```
 
 A good example of a plugin is the built-in plugin for the `<py-script>` tag
-found in `pyscript.js` (search for pyScriptTag).
+found in `pyscript.js` (search for the object assigned to `pyScriptTag`).
 
 ## Runtimes
 
diff --git a/pyscript.js b/pyscript.js
@@ -33,16 +33,17 @@ const main = function() {
 
     * Keep the bare minimum of state.
     * Load and process any configuration from the page.
-    * Provide a mechanism for PyScriptPlugin based plugins to be registered,
-      configured and then started.
+    * Provide a mechanism for plugins to be registered, configured and then
+      started.
     * Load and start the Python runtime.
     * Dispatch the following events to signal various changes in state or the
       completion of tasks (such as starting the runtime).
         - "py-configured", when configuration is processed.
         - "py-plugin-registered", when a plugin is registered.
+        - "py-plugin-started", when a plugin is started.
         - "py-runtime-loaded", when the runtime has been downloaded.
         - "py-runtime-ready", when the runtime is ready to process Python.
-    * Define, configure and start the built-in PyScript plugins (e.g. the 
+    * Define, configure and start built-in PyScript plugins (e.g. the 
       <py-script> tag).
     **************************************************************************/
 
@@ -338,11 +339,6 @@ const main = function() {
         }
     }
 
-    // An object to represent the PyScript platform in the browser. What is
-    // eventually returned from the main() function.
-    const PyScript = {
-    }
-
     // Default configuration settings for PyScript. These may be overridden by
     // the app.loadConfig function.
     const config = {
