Implement test spec review suggestions

Co-authored-by: Volker Häussler <volker.haeussler@qorix.ai>
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>

Author: pahmann

process/process_areas/verification/guidance/verification_guideline.rst

@@ -17,7 +17,7 @@ Guideline
 .. gd_guidl:: Verification Guideline
    :id: gd_guidl__verification_guide
    :status: valid
-   :version: 1
+   :version: 2
    :complies: std_req__isopas8926__445[version==1]
 
    This guideline outlines the responsibilities and procedures for developers performing

process/process_areas/verification/verification_concept.rst

@@ -18,7 +18,7 @@ Concept Description
 .. doc_concept:: Verification Concept
    :id: doc_concept__verification_process
    :status: valid
-   :version: 1
+   :version: 2
    :tags: requirements_engineering
 
    In this section a concept for the verification activities will be discussed.
@@ -160,10 +160,10 @@ tests or component tests. This linking is done using metatags. This is also true
 integration tests linking to the component requirements and architecture.
 
 Traceability of feature integration tests shall be established through linking those test cases to
-feature requirements and architecture as features describe the integrated behavior of all components.
+feature requirements and architecture as features describe the integrated behaviour of all components.
 
 Traceability of platform integration tests shall be established through linking those test cases to
-stakeholder requirements as stakeholder requirements describe the platform behavior.
+stakeholder requirements as stakeholder requirements describe the platform behaviour.
 
 Note that all the above tests shall only link to requirements of type "Functional" and "Interface".
 The verification of requirements of types "Process" and "Non-Functional" will be done via Analysis,