diff --git a/process/process_areas/configuration_management/configuration_concept.rst b/process/process_areas/configuration_management/configuration_concept.rst
index 9bf0deb815..b3ed11d9e6 100644
--- a/process/process_areas/configuration_management/configuration_concept.rst
+++ b/process/process_areas/configuration_management/configuration_concept.rst
@@ -51,3 +51,11 @@ Stakeholders
    * wants know which work products's version has to be used as input for his work
    * wants to share their created work product with others for example to get those reviewed
    * wants to integrate their created work product with other work products
+
+Configuration Management Tooling
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Almost all requirements of the standards towards configuration management can be covered by
+standard versioning tooling and of tooling for the "Docs-as-Code" approach.
+
+For the automated storage additional tooling is needed see :doc:`guidance/configuration_process_req`)
diff --git a/process/process_areas/configuration_management/index.rst b/process/process_areas/configuration_management/index.rst
index 7df75ef837..21b476404c 100644
--- a/process/process_areas/configuration_management/index.rst
+++ b/process/process_areas/configuration_management/index.rst
@@ -17,15 +17,6 @@
 Configuration Management
 ========================
 
-Configuration Management Tooling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Almost all requirements of the standards towards configuration management can be covered by
-standard tooling of the Eclipse Foundation (github for versioning) and of the S-CORE project
-(sphinx-needs for text based identification of work products).
-
-For the automated storage additional tooling is created (see :doc:`guidance/configuration_process_req`)
-
 .. toctree::
    :maxdepth: 1