diff --git a/src/doc/extension/forms.rst b/src/doc/extension/forms.rst
index d5ede1b1aeef9365df2d170fda3cd17d6cbf3e85..94cab0f48ba6dbd95b432f2e99b336f129bfdedc 100644
--- a/src/doc/extension/forms.rst
+++ b/src/doc/extension/forms.rst
@@ -49,14 +49,26 @@ As the generated form is a plain HTML form, the javascript form API can be used.
 Placing the form in a panel below the navbar
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-There are functions in the `form_panel` module to make it easy to place forms at the typical location: 
-below the navbar. The following shows how the config (see above) is passed to 
-`init_show_form_panel_button`  a direct call to `make_form` is no longer necessary.
+There are functions in the ``form_panel`` module to make it easy to place forms at the typical location:
+below the navbar. The following shows how the config (``csv_form_config``, see above) is passed to
+``init_show_form_panel_button``. A direct call to `make_form` is no longer necessary.
 
 .. code-block:: javascript
 
     const title = "Upload CSV File"; // title of the form and text in the toolbox
     const panel_id = "csv_upload_form_panel";
+    const accepted_file_formats = [".csv"]
+    const csv_form_config = {
+        fields: [{
+            type: "file",
+            name: "csvfile",
+            label: "Upload CSV file",
+            required: true,
+            cached: false,
+            accept: accepted_file_formats.join(","),
+            help: "Select JSON export that you want to upload."
+        }],
+    };
 
     /**
      * Add a button to the navbar, saying "Upload CSV File" which opens a
@@ -75,36 +87,37 @@ below the navbar. The following shows how the config (see above) is passed to
         init_show_form_panel_button();
     }
 
+This example also illustrates how you can add a file upload to the form.
+
 Calling a server-side script
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-If you intend to call a server-side script, the config has to be changed a litte bit and the script calling is done by the ``form_elements`` module. There is no need to define the submit_hander anymore. Instead, just name the script which is to be called.
+If you intend to call a server-side script, the config has to be changed a litte bit:
+name the script which is to be called in the ``script`` field.
 
 .. code-block:: javascript
 
     const config = {
         script: "process.py",
         fields: [
-            { type: "reference_drop_down", name: "experiment_id", label: "Experiment", query: "FIND Experiment", required: true },
-            { type: "integer", name: "number", label: "A Number", required: true },
-            { type: "date", name: "date", label: "A Date", required: false },
-            { type: "text", name: "comment", label: "A Comment", required: false },
+            { type: "integer", name: "number", label: "A Number", required: true }
         ],
     };
-    const form = form_elements.make_form(config);
-    $("body").append(form);
 
 On submission, the form data will be send as a json file to the script and passed as the first parameter. The call would look like ``./process.py form.json`` and the file would contain, for example,
 
 .. code-block:: json
 
     {
-      "experiment_id": "234234",
-      "number": "400",
-      "date": "2020-12-24",
-      "comment": "This is a comment",
+      "number": "400"
     }
 
-For more and advanced options for the form see the :doc:`API documentation <../api/module-form_elements>`
+Please refer to the `server side scripting documentation
+<https://docs.indiscale.com//caosdb-server/administration/server_side_scripting.html>`_
+to learn how to use form data and uploaded files within a server side script.
 
 
+API Documentation
+--------
+
+For more and advanced options for the form see the :doc:`API documentation <../api/module-form_elements>`
diff --git a/src/doc/extension/module.md b/src/doc/extension/module.md
index 14eae2afd89365fee056cbfce069fb8b434836a0..284b4dcf6d7f6b5fc654fd075727b878e2a57b2e 100644
--- a/src/doc/extension/module.md
+++ b/src/doc/extension/module.md
@@ -51,7 +51,7 @@ $(document).ready(function() {
     // use a variable starting with `BUILD_MODULE_` to enable your module
     // the build variable has to be enabled in the `build.properties.d/` directory.
     // Otherwise the module will not be activated.
-    if ("${BUILD_MODULE_EXT_BOTTOM_LINE}" === "ENABLED") {
+    if ("${BUILD_MODULE_EXT_FLIGHT_PREVIEW}" === "ENABLED") {
         caosdb_modules.register(ext_flight_preview);
     }
 });
@@ -88,4 +88,17 @@ may append all your module files in the desired order to the
 
     MODULE_DEPENDENCIES+=(libA.js libB.js ext_flight_preview.js)
 
-In this example, `libA.js`, `libB.js` and `ext_flight_preview.js` are custom modules developed for this particular LinkAhead webui instance.
+In this example, `libA.js`, `libB.js` and `ext_flight_preview.js` are custom modules developed for this particular CaosDB webui instance.
+
+Briefly describe the changes you made to the whole repository in the file called `CHANGELOD.md` in caosdb-webui.
+
+## Create a merge request
+
+Commit your changes to the repository to a new branch called `f-<custom name>`. `f-` is the shorthand for feature-branch and your custom name should be short, but descriptive, e.g. `f-flight-preview` in this case.
+
+Push your branch upstream using e.g.:
+`git push --set-upstream origin f-flight-preview`
+
+Login to gitlab and navigate to the project caosdb-webui.
+
+There should be a button titled `Create Merge Request`.
\ No newline at end of file