fixed #168, "concerns" -> "concepts" in LG 1-4, 2-4 and 3-6

Author: gernotstarke

docs/01-basics/LZ-1-04.adoc

@@ -31,7 +31,7 @@ Tasks and responsibilities of software architects:
 * Clarify and scrutinize requirements and constraints, and refine them if necessary.
 Together with functional requirements (required features), this includes the required quality characteristics (_required constraints_).
 * Decide how to decompose the system into building blocks, while determining dependencies and interfaces between the building blocks.
-* Determine and decide on cross-cutting concerns (for instance persistence, communication, GUI etc.)
+* Determine and decide on cross-cutting concepts (for instance persistence, communication, GUI etc.)
 * Communicate and document software architecture based on views, architectural patterns, cross-cutting and technical concepts
 * Accompany the realization and implementation of the architecture; integrate feedback from relevant stakeholders into the architecture if necessary; review and ensure the consistency of source code and software architecture
 * Analyze and evaluate software architecture, especially with respect to risks involving the quality requirements

docs/02-design/LZ-2-04.adoc

@@ -15,21 +15,18 @@ Softwarearchitekt:innen wissen, dass solche Querschnittskonzepte systemübergrei
 
 // tag::EN[]
 [[LG-2-4]]
-==== LG 2-4: Design and implement cross-cutting concerns (R1)
+==== LG 2-4: Design and implement cross-cutting concepts (R1)
 
 Software architects are able to:
 
-* explain the significance of such cross-cutting concerns
-* decide on and design cross-cutting concerns, for example persistence, communication, GUI, error handling, concurrency
+* explain the significance of such cross-cutting concepts
+* decide on and design cross-cutting concepts, for example persistence, communication, GUI, error handling, concurrency
 * identify and assess potential interdependencies between these decisions.
 
 Software architects know that such cross-cutting concepts may be re-used throughout the system.
 
 // end::EN[]
 
 // tag::REMARK[]
-[NOTE]
-====
-GS/CL: leicht umformuliert. Modified EN translation of "Konzept" to "concept" instead of "concern".
-====
+
 // end::REMARK[]

docs/03-documentation/LZ-3-06.adoc

@@ -10,18 +10,12 @@ Softwarearchitekt:innen können typische Querschnittskonzepte (synonym _Prinzipi
 
 // tag::EN[]
 [[LG-3-6]]
-==== LG 3-6: Document and communicate cross-cutting concerns (R1)
+==== LG 3-6: Document and communicate cross-cutting concepts (R1)
 
 Software architects are able to adequately document and communicate typical cross-cutting concepts (synonym: _principles_, _aspects_), e. g., persistence, workflow management, UI, deployment/integration, logging.
 
 // end::EN[]
 
 // tag::REMARK[]
 
-[NOTE]
-====
-
-* GS+RR: Redundanz zu Kapitel 2 entfernt, Protokollierung aufgenomen.
-* JR: Begriff an Kapitel 2 angepasst: "Querschnittskonzepte" anstelle von "querschnittliche Konzepte".
-====
 // end::REMARK[]