[qa] Formatted docs

.github/workflows/ci.yml

@@ -68,11 +68,11 @@ jobs:
       - name: Tests
         if: ${{ !cancelled() && steps.deps.conclusion == 'success' }}
         run: |
-          coverage run runtests.py --parallel || ./runtests.py
+          coverage run --parallel-mode runtests.py --parallel || ./runtests.py
+          coverage combine
           MONITORING_INTEGRATION=1 coverage run --append runtests.py
           # SAMPLE tests do not influence coverage, so we can speed up tests with --parallel
           SAMPLE_APP=1 coverage run ./runtests.py --parallel > /dev/null 2>&1 || SAMPLE_APP=1 ./runtests.py
-          coverage combine
           coverage xml
 
       - name: Upload Coverage

docs/user/radius_monitoring.rst

@@ -4,7 +4,8 @@ Integration with OpenWISP Monitoring
 ====================================
 
 OpenWISP RADIUS includes an optional Django sub-app that adds integration
-with :doc:`OpenWISP Monitoring </monitoring/index>` to provide RADIUS metrics.
+with :doc:`OpenWISP Monitoring </monitoring/index>` to provide RADIUS
+metrics.
 
 .. image:: ../images/radius-dashboard-charts.png
     :alt: RADIUS session dashboard charts
@@ -65,10 +66,10 @@ Django project's settings as following:
 .. note::
 
     Ensure your Django project is correctly configured to utilize OpenWISP
-    Monitoring. For production environments, it is advisable to deploy OpenWISP using
-    :doc:`Ansible OpenWISP </ansible/index>`
-    or :doc:`Docker OpenWISP </docker/index>`,
-    as they simplify the deployment process considerably.
+    Monitoring. For production environments, it is advisable to deploy
+    OpenWISP using :doc:`Ansible OpenWISP </ansible/index>` or
+    :doc:`Docker OpenWISP </docker/index>`, as they simplify the
+    deployment process considerably.
 
 .. important::
 

pyproject.toml

@@ -1,6 +1,5 @@
 [tool.coverage.run]
 source = ["openwisp_radius"]
-parallel = true
 concurrency = ["multiprocessing"]
 omit = [
     "openwisp_radius/__init__.py",