Increment prerelease version number to 0.4.0

Author: Mark Gibbs

django_plotly_dash/__init__.py

@@ -1,6 +1,6 @@
 #
 
-__version__ = "0.3.0"
+__version__ = "0.4.0"
 
 from .dash_wrapper import DjangoDash
 

docs/installation.rst

@@ -15,7 +15,7 @@ Then, add ``django_plotly_dash`` to ``INSTALLED_APPS`` in the Django ``settings.
         ...
         ]
 
-The project directory name ``django_plotly_dash`` can also be used on its own if preferred, but this will then skip the use of readable application names in
+The project directory name ``django_plotly_dash`` can also be used on its own if preferred, but this will stop the use of readable application names in
 the Django admin interface.
 
 The application's routes need to be registered within the routing structure by an appropriate ``include`` statement in
@@ -26,13 +26,17 @@ a ``urls.py`` file::
         path('django_plotly_dash/', include('django_plotly_dash.urls')),
     ]
 
-Finally, a migration is needed to update the
+The name within the URL is not important and can be changed.
+
+For the final installation step, a migration is needed to update the
 database::
 
     ./manage.py migrate
 
 The ``plotly_item`` tag in the ``plotly_dash`` tag library can then be used to render any registered dash component. See :ref:`simple_use` for a simple example.
 
+It is important to ensure that any applications are registered using the ``DjangoDash`` class. This means that any python module containing the registration code has to be known to Django and loaded at the appropriate time. An easy way to ensure this is to import these modules into a standard Django file loaded at registration time.
+
 Source code and demo
 --------------------
 
@@ -54,3 +58,6 @@ To install and run it::
 
 This will launch a simple Django application. A superuser account is also configured, with both username and password set to ``admin``.
 
+Note that the current demo, along with the codebase, is in a prerelease and very raw form.
+
+