fix review findings

Author: masc2023

process/glossary/index.rst

@@ -81,6 +81,10 @@ Terms
      - A packaging mechanism for delivering Dependable Elements (e.g., executable code or libraries) to users or integrators of the platform.
      - :ref:`Building blocks concept<general_concepts_building_blocks>`
 
+   * - **Delivery Team**
+     - Cross-functional team responsible for all artifacts within a Module, including development, quality, safety, and security activities.
+     - :ref:`Roles<roles>`
+     -
    * - **Dependable Element**
      - The highest abstraction level in the building blocks model. A Dependable Element consists of one or more Components and can be developed as a Safety Element out of Context (SEooC). It is delivered in a Delivery Container.
      - :ref:`Building blocks concept<general_concepts_building_blocks>`
@@ -117,6 +121,10 @@ Terms
      - Systematic analysis performed on feature architecture to verify compliance with safety and security requirements at the feature level, documenting any violations or potential faults.
      - ::ref:`Building blocks concept<general_concepts_building_blocks>`
 
+   * - **Feature Team**
+     - An synonym term for Delivery Team.
+     - :ref:`Roles<roles>`
+
    * - **Impact Analysis**
      - The process of evaluating the effects and consequences of proposed changes on work products.
      - :ref:`Process change management<change_management>`
@@ -137,10 +145,6 @@ Terms
      - An synonym term for Dependable Element
      - :ref:`Building blocks concept<general_concepts_building_blocks>`
 
-   * - **Module Team**
-     - Cross-functional team responsible for all artifacts within a Module, including development, quality, safety, and security activities.
-     - :ref:`Roles<roles>`
-
    * - **Platform**
      - The complete software platform consisting of features, components, and supporting infrastructure.
      - :ref:`Building blocks concept<general_concepts_building_blocks>`

process/process_areas/change_management/guidance/change_management_guideline.rst

@@ -43,7 +43,9 @@ to provide e.g. a change request issue template.
 .. note::
   An example template for the Issue Tracking System in GitHub (`GitHub Issues <https://github.com/features/issues>`_)
   can be found here:
-  `Issue Template Change Request <https://github.com/eclipse-score/.github/blob/main/.github/ISSUE_TEMPLATE/1a_FeatureRequest.yml>`_
+  `Issue Template Change (Feature) Request <https://github.com/eclipse-score/.github/blob/main/.github/ISSUE_TEMPLATE/1a_FeatureRequest.yml>`_
+  or
+  `Issue Template Change (Component) Request <https://github.com/eclipse-score/.github/blob/main/.github/ISSUE_TEMPLATE/1b_ComponentenRequest.yml>`_
 
 Improvements including Process Improvements are not Change Requests.
 The project's selected Issue Tracking System may also provide a template for improvements,
@@ -128,7 +130,9 @@ automatically included or copied by the different users.
 .. note::
   For the Issue Tracking System in GitHub, there is a template created, which can be
   be found here:
-  `Issue Template Change <https://github.com/eclipse-score/.github/blob/main/.github/ISSUE_TEMPLATE/1a_FeatureRequest.yml>`_
+  `Issue Template Change (Feature) Request <https://github.com/eclipse-score/.github/blob/main/.github/ISSUE_TEMPLATE/1a_FeatureRequest.yml>`_
+  or
+  `Issue Template Change (Component) Request <https://github.com/eclipse-score/.github/blob/main/.github/ISSUE_TEMPLATE/1b_ComponentenRequest.yml>`_
 
 .. note::
   A Change Request Example based on that template is here: