diff --git a/docs/src/11_technical_risks.adoc b/docs/src/11_technical_risks.adoc
index dc5575fc..a75e08fd 100644
--- a/docs/src/11_technical_risks.adoc
+++ b/docs/src/11_technical_risks.adoc
@@ -6,20 +6,13 @@ ifndef::imagesdir[:imagesdir: ../images]
 
 [role="arc42help"]
 ****
-.Contents
-A list of identified technical risks or technical debts, ordered by priority
 
-.Motivation
-“Risk management is project management for grown-ups” (Tim Lister, Atlantic Systems Guild.) 
+[options="header"]
+|===
+|Risk                       |Consequence
 
-This should be your motto for systematic detection and evaluation of risks and technical debts in the architecture, which will be needed by management stakeholders (e.g. project managers, product owners) as part of the overall risk analysis and measurement planning.
-
-.Form
-List of risks and/or technical debts, probably including suggested measures to minimize, mitigate or avoid risks or reduce technical debts.
-
-
-.Further Information
-
-See https://docs.arc42.org/section-11/[Risks and Technical Debt] in the arc42 documentation.
+|Knowledge of REACT         |It is a framework that no team member has used before. Therefore, we have all had to learn how to use it. 
+|Internal group conflicts   |Lack of free time for team members makes group work difficult. 
+|===
 
 ****