Switch from direct to generated metrics

Author: ArBridgeman

doc/user_guide/features/metrics/collecting_metrics.rst

@@ -7,10 +7,10 @@ Collecting metrics
     project_report
     sonar
 
-.. _direct_metrics:
+.. _generated_metrics:
 
-Direct metrics
-++++++++++++++
+Generated metrics
++++++++++++++++++
 
 The PTB allows you to collect various metrics on the quality of your project
 regarding Coverage, Security, and Static Code Analysis.
@@ -48,7 +48,7 @@ The GitHub workflows of your project can:
 Reporting metrics
 +++++++++++++++++
 
-Currently, the PTB offers two methods to aggregate the :ref:`direct_metrics`
+Currently, the PTB offers two methods to aggregate the :ref:`generated_metrics`
 into a report:
 
 #. the nox session ``project:report``
@@ -59,7 +59,7 @@ into a report:
     `Sonar <https://docs.sonarsource.com/sonarqube-server/latest/>`__. For further
     details, see :ref:`sonarqube_analysis`
 
-Both of these reporting options require that the generated files from the :ref:`direct_metrics`
+Both of these reporting options require that the generated files from the :ref:`generated_metrics`
 are existing and in the expected formats. As we have metrics for different Python
 versions, we pass on the metrics associated with the Python version named first in
 attribute ``python_versions`` of class ``Config`` to the reporting metrics tools.

doc/user_guide/features/metrics/project_report.rst

@@ -3,7 +3,7 @@
 ``project:report``
 ==================
 The nox session ``project:report`` provides an overall coverage percentage,
-maintainability grade, and security grade based on the :ref:`direct_metrics` collected.
+maintainability grade, and security grade based on the :ref:`generated_metrics` collected.
 The definitions used for evaluating the quality of the Python code is defined in the
 `metrics.py`_ file, and the required fields are specified by the code-agnostic
 :ref:`metrics_schema` for Exasol. This nox session can return its analysis in two forms:
@@ -22,7 +22,7 @@ The definitions used for evaluating the quality of the Python code is defined in
 
 Metrics schema
 ++++++++++++++
-The PTB supports the uniform json schema for metrics used by all projects 
+The PTB supports the uniform json schema for metrics used by all projects
 of the Exasol Product Integration Team:
 
 * `Exasol Schemas`_