fix packages

dom.rst

@@ -9,8 +9,8 @@ The DOM is built starting with an `Element <https://github.com/kwebio/kweb-core/
 
 .. code-block:: kotlin
 
-   import io.kweb.*
-   import io.kweb.dom.element.*
+   import kweb.*
+   import kweb.dom.element.*
 
    fun main() {
      Kweb(port = 16097) {
@@ -23,8 +23,8 @@ supported by all Element types):
 
 .. code-block:: kotlin
 
-   import io.kweb.*
-   import io.kweb.dom.element.*
+   import kweb.*
+   import kweb.dom.element.*
 
    fun main() {
      Kweb(port = 16097) {
@@ -67,11 +67,11 @@ Kweb can also read from the DOM, in this case the value of an <input> element:
 
 .. code-block:: kotlin
 
-    import io.kweb.Kweb
-    import io.kweb.dom.element.creation.tags.*
-    import io.kweb.dom.element.events.on
-    import io.kweb.dom.element.new
-    import io.kweb.state.KVar
+    import kweb.Kweb
+    import kweb.dom.element.creation.tags.*
+    import kweb.dom.element.events.on
+    import kweb.dom.element.new
+    import kweb.state.KVar
     import kotlinx.coroutines.GlobalScope
     import kotlinx.coroutines.future.await
     import kotlinx.coroutines.launch

events.rst

@@ -35,7 +35,7 @@ Since the code to respond to events runs on the server, there may be a short lag
 event and any changes to the DOM caused by the event handler.  This was a common complaint about previous server-driven
 web frameworks like Vaadin, inhibiting their adoption.
 
-Fortunately, Kweb has a solution - `onImmediate <https://jitpack.io/com/github/kwebio/core/0.3.15/javadoc/io.kweb.dom.element.events/on-immediate.html>`_:
+Fortunately, Kweb has a solution:
 
 .. code-block:: kotlin
 

gettingstarted.rst

@@ -40,9 +40,9 @@ Create a new Kotlin file and type this:
 
 .. code-block:: kotlin
 
-   import io.kweb.*
-   import io.kweb.dom.element.*
-   import io.kweb.dom.element.creation.tags.*
+   import kweb.*
+   import kweb.dom.element.*
+   import kweb.dom.element.creation.tags.*
 
    fun main() {
      Kweb(port = 16097) {
@@ -80,9 +80,9 @@ Here is a simple example using an ordinary Kotlin *for loop*:
 
 .. code-block:: kotlin
 
-   import io.kweb.*
-   import io.kweb.dom.element.*
-   import io.kweb.dom.element.creation.tags.*
+   import kweb.*
+   import kweb.dom.element.*
+   import kweb.dom.element.creation.tags.*
 
    fun main() {
      Kweb(port = 16097) {

routing.rst

@@ -19,10 +19,10 @@ A simple example
 
 .. code-block:: kotlin
 
-    import io.kweb.Kweb
-    import io.kweb.dom.element.new
-    import io.kweb.dom.element.creation.tags.h1
-    import io.kweb.routing.route
+    import kweb.Kweb
+    import kweb.dom.element.new
+    import kweb.dom.element.creation.tags.h1
+    import kweb.routing.route
 
     fun main() {
         Kweb(port = 16097) {
@@ -84,11 +84,11 @@ page URL:
 
 .. code-block:: kotlin
 
-    import io.kweb.Kweb
-    import io.kweb.dom.element.creation.tags.a
-    import io.kweb.dom.element.new
-    import io.kweb.routing.route
-    import io.kweb.state.*
+    import kweb.Kweb
+    import kweb.dom.element.creation.tags.a
+    import kweb.dom.element.new
+    import kweb.routing.route
+    import kweb.state.*
 
     fun main() {
         Kweb(port = 16097) {

style.rst

@@ -12,7 +12,7 @@ First tell Kweb to use the Fomantic UI plugin:
 
 .. code-block:: kotlin
 
-    import io.kweb.plugins.fomanticUI.*
+    import kweb.plugins.fomanticUI.*
 
     fun main() {
         Kweb(port = 16097, plugins = listOf(fomanticUIPlugin)) {
@@ -36,8 +36,8 @@ This translates to the Kotlin:
 
 .. code-block:: kotlin
 
-    import io.kweb.plugins.fomanticUI.*
-    import io.kweb.dom.element.creation.tags.InputType.*
+    import kweb.plugins.fomanticUI.*
+    import kweb.dom.element.creation.tags.InputType.*
 
     fun main() {
         Kweb(port = 16097, plugins = listOf(fomanticUIPlugin)4) {