Metamodel link renames

Relates: #418

Author: aschemmel-tech

process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst

@@ -81,7 +81,7 @@ See also :need:`doc_concept__wp_inspections` for further information about revie
       -
     * - ARC_01_03
       - If the architectural element is related to any supplier manuals (including safety and security), are the relevant parts covered?
-      - If the architecture makes use of supplied elements, their manuals (like safety) have to be considered (i.e. its provided functionality matches the expectation and assumptions are fulfilled). Note that in case of safety component this means that assumed Technical Safety Requirements and AoUs of the safety manual are covered.
+      - If the architecture makes use of supplied elements, their manuals (like safety) have to be considered (i.e. its provided functionality matches the expectation and assumptions are satisfied). Note that in case of safety component this means that assumed Technical Safety Requirements and AoUs of the safety manual are covered.
       -
       -
       -

process/folder_templates/features/feature_name/requirements/chklst_req_inspection.rst

@@ -132,7 +132,7 @@ See also :need:`doc_concept__wp_inspections` for further information about revie
       -
     * - REQ_07_02
       - Is the *security* attribute set correctly?
-      - For feature requirements this checklist item is supported by automated check: "Every requirement which satisfies a stakeholder requirement with security attribute set to YES inherits this". But the feature requirements/architecture may additionally also be subject to a :need:`wp__feature_security_analysis`
+      - For feature requirements this checklist item is supported by automated check: "Every requirement which is derived from a stakeholder requirement with security attribute set to YES inherits this". But the feature requirements/architecture may additionally also be subject to a :need:`wp__feature_security_analysis`
       -
       -
       -

process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst

@@ -82,7 +82,7 @@ See also :need:`doc_concept__wp_inspections` for further information about revie
     * - ARC_01_03
       - If the architectural element is related to any supplier manuals (incl. safety and security)
         are the relevant parts covered?
-      - If the architecture makes use of supplied elements, their manuals (like safety) have to be considered (i.e. its provided functionality matches the expectation and assumptions are fulfilled). Note that in case of safety component this means that assumed Technical Safety Requirements and AoUs of the safety manual are covered.
+      - If the architecture makes use of supplied elements, their manuals (like safety) have to be considered (i.e. its provided functionality matches the expectation and assumptions are satisfied). Note that in case of safety component this means that assumed Technical Safety Requirements and AoUs of the safety manual are covered.
       -
       -
       -

process/folder_templates/modules/module_name/component_name/docs/requirements/chklst_req_inspection.rst

@@ -132,7 +132,7 @@ See also :need:`doc_concept__wp_inspections` for further information about revie
       -
     * - REQ_07_02
       - Is the attribute *security* set correctly?
-      - For component requirements this checklist item is supported by automated check: "Every requirement which satisfies a feature requirement with security attribute set to YES inherits this". But the component requirements/architecture may additionally also be subject to a :need:`wp__sw_component_security_analysis`.
+      - For component requirements this checklist item is supported by automated check: "Every requirement which derives from a feature requirement with security attribute set to YES inherits this". But the component requirements/architecture may additionally also be subject to a :need:`wp__sw_component_security_analysis`.
       -
       -
       -