Update & publish new doc versions

docs/main/_sources/flame/components.md.txt

@@ -47,7 +47,7 @@ it is only run once even if the component is removed both by using the parents r
 the `Component` remove method.
 
 The `onLoad` method can be overridden to run asynchronous initialization code for the component,
-like loading an image for example. This method is executed after `onGameResize`, but before
+like loading an image for example. This method is executed before `onGameResize` and
 `onMount`. This method is guaranteed to execute only once during the lifetime of the component, so
 you can think of it as an "asynchronous constructor".
 

docs/main/flame/components.html

@@ -451,7 +451,7 @@ <h3>Component lifecycle<a class="headerlink" href="#component-lifecycle" title="
 it is only run once even if the component is removed both by using the parents remove method and
 the <code class="docutils literal notranslate"><span class="pre">Component</span></code> remove method.</p>
 <p>The <code class="docutils literal notranslate"><span class="pre">onLoad</span></code> method can be overridden to run asynchronous initialization code for the component,
-like loading an image for example. This method is executed after <code class="docutils literal notranslate"><span class="pre">onGameResize</span></code>, but before
+like loading an image for example. This method is executed before <code class="docutils literal notranslate"><span class="pre">onGameResize</span></code> and
 <code class="docutils literal notranslate"><span class="pre">onMount</span></code>. This method is guaranteed to execute only once during the lifetime of the component, so
 you can think of it as an “asynchronous constructor”.</p>
 <p>The <code class="docutils literal notranslate"><span class="pre">onMount</span></code> method runs every time when the component is mounted into a game tree. This means that