Workflow.md

@@ -4,14 +4,13 @@ In order to fully use the capabilities of GitLab it is necessary to establish a
 
 * Localized changes (don't change the whole system at once but by parts)
 * Localized notification
-* Localized responsibility
-*
+* Localized assurance (technical and editorial quality assurance)
 
 ## Localized Change
 
-This does not mean to only change a file, but to have one dedicated issue/merge-request for a concrete problem. Branches will be deleted after merge.
+This does not mean to only change a file, but to have one dedicated issue/merge-request for a concrete problem. Branches will be deleted after merge (Repository setting). There are standard rules about how large commits etc. should be...
 
-## Localized Notification
+## Localized Notification and (Quality) Assurance
 
 By the use of [labels](https://collaborating.tuhh.de/cfg0846/research-topics-mat-tuhh/-/labels), the classification of issues allows to only notify the ones that are needed during the handling of the follow-up merge-request:
 
@@ -33,9 +32,9 @@ Technicians should subscribe to the following labels:
 
 These labels are then specified to inform technical maintainers that something about the webpage, repo does not work as expected or to classify development projects that do not add new functionality (e.g. [code refactoring](https://en.wikipedia.org/wiki/Code_refactoring).
 
-### Redactional Labels
+### Editorial Labels
 
-Professors, Chief-Engineers and other people responsible for redactional quality assurance should subscribe to at least one of the following labels:
+Professors, Chief-Engineers and other people responsible for editorial quality assurance should subscribe to at least one of the following labels:
 
 * `aa-content`
 * `cm-content`