Update broken references (#923)

Signed-off-by: Emmanuel Ferdman <emmanuelferdman@gmail.com>

examples/todomvc/src/jsMain/resources/index.html

@@ -13,7 +13,7 @@
 <footer class="info">
     <p>Double-click to edit a todo</p>
     <p>Source at <a
-            href="https://github.com/jwstegemann/fritz2/blob/master/examples/todomvc/src/jsMain/kotlin/dev/fritz2/examples/todomvc/todomvc.kt">github</a>
+            href="https://github.com/jwstegemann/fritz2/blob/master/examples/todomvc/src/jsMain/kotlin/dev/fritz2/examples/todomvc/TodoMvc.kt">github</a>
     </p>
     <!-- Change this out with your name and url ↓ -->
     <p>Created by <a href="https://github.com/jwstegemann/fritz2">jwstegemann & jamowei</a></p>

www/src/blog/posts/paradigm-shift-for-components.md

@@ -263,7 +263,7 @@ In addition, one would still have to style each building block accordingly withi
 and fully functional surface unit, which was omitted here for reasons of space and simplicity. In principle, one injects
 the styling into the function block as the first parameter, analogous to the known tag factory functions. The source
 code of
-the [example for a RadioGroup](https://github.com/jwstegemann/fritz2/blob/master/headless-demo/src/jsMain/kotlin/dev/fritz2/headlessdemo/radioGroup.kt)
+the [example for a RadioGroup](https://github.com/jwstegemann/fritz2/blob/master/headless-demo/src/jsMain/kotlin/dev/fritz2/headlessdemo/components/RadioGroup.kt)
 from the `headless-demo` project clearly shows that the styling specifications make the whole thing only slightly more
 complex.
 

www/src/pages/docs/45_EventHandling.md

@@ -14,7 +14,7 @@ eleventyNavigation:
 
 In fritz2, all HTML-Events are either encapsulated within a `Tag`-scope or within the special `Window`-object, which both
 offer access to all global events. A complete list can be found in the
-[events.kt](https://github.com/jwstegemann/fritz2/blob/master/core/src/jsMain/kotlin/dev/fritz2/core/events.kt) file.
+[Events.kt](https://github.com/jwstegemann/fritz2/blob/master/core/src/jsMain/kotlin/dev/fritz2/core/Events.kt) file.
 
 The most important aspect to understand is that an event in fritz2 is just a type derived by `Flow`. You can
 use all events as the source of an action which should be handled by a handler-function.
@@ -452,4 +452,4 @@ div {
         //  based upon any other `Flow`-source`
     }
 }
-```
+```