diff --git a/docs/use/pelican.rst b/docs/use/pelican.rst
index 346b023c..0d3fd99c 100644
--- a/docs/use/pelican.rst
+++ b/docs/use/pelican.rst
@@ -29,14 +29,10 @@ After a few seconds, you should see your report being processed at https://pelic
`Pelican frontend's web API documentation `__
-Delete a report
----------------
-
-Once you no longer need a report, remember to delete it, replacing ``1`` with its ID:
-
-.. code-block:: bash
+Check on progress
+-----------------
- curl -n -X DELETE https://pelican.open-contracting.org/api/datasets/1/
+https://pelican.open-contracting.org indicates the status of reports. In general, this is sufficient. However, you can use the RabbitMQ management interface to check that work isn't stuck, :ref:`like for Kingfisher Process`, instead reading the ``pelican_backend_`` rows.
Read and export a report
------------------------
@@ -48,7 +44,11 @@ To `export a report `__. To use another template, share it with data-tools@open-contracting.org.
- Export folder ID: ``1ZVwf9cr29E4uCuWaVRiQLJI7_ejE00h3`` to use `this folder `__. To use another folder, share it with data-tools@open-contracting.org.
-Check on progress
------------------
+Delete a report
+---------------
-https://pelican.open-contracting.org indicates the status of reports. In general, this is sufficient. However, you can use the RabbitMQ management interface to check that work isn't stuck, :ref:`like for Kingfisher Process`, instead reading the ``pelican_backend_`` rows.
+Once you no longer need a report, remember to delete it, replacing ``1`` with its ID:
+
+.. code-block:: bash
+
+ curl -n -X DELETE https://pelican.open-contracting.org/api/datasets/1/