docs/git/Workflow.md

@@ -25,12 +25,9 @@ In a nutshell (click the individual steps for detailed guidelines):
 1. When creating an issue, select a relevant template. This will provide you a basic template to fill out and assign some initial labels to the issue\
 ~Feature  ~Question  ~Bug
 
-1. If you already know what group the issue is relevant for, add it as a label, e.g.:\
+1. If you already know what group or WP the issue is relevant for, add it as a label, e.g.:\
 ~Actions&Controllers ~SensorModeling ~HarmonisationOpenX ~Performance&Packaging
 
-1. If you know what WP the issue is for, add it as a label, e.g.:\
-~WP-V2X  ~"WP-OSI as a measurement file"
-
 1. If you already know what part of the standard the issue will impact, add the corresponding label.
 ~Model ~Documentation
 
@@ -38,7 +35,7 @@ See [Label Types](../git/ASAM-Issue-and-MR-Labels) for an overview of available
 
 # Issue Review
 
-The Change Control Board(CCB) (see [ASAM Project Roles](/docs/project_guidelines/ASAM-Project-Roles#asam-change-control-board)) is expected to regularly review and maintain the issues in the repository. CCB members will review any new issues and either answer them directly (if of type ~Question ) or categorise the issues and assign them to a project group for further review. If it is decided that the issue should be addressed and requires further discussion or implementation, it is assigned the ~Analysis label.
+All project members are expected to regularly review the issues in the project. Additionally the Change Control Board(CCB) (see [ASAM Project Roles](/docs/project_guidelines/ASAM-Project-Roles#asam-change-control-board)) is expected to support. Members will review any new issues and either answer them directly (if of type ~Question ) or categorise the issues and assign them to a project group for further review. If it is decided that the issue should be addressed and requires further discussion or implementation, it is assigned the ~Analysis label.
 
 # Expert Discussion