From 327ecd0038b22fa4dbdaddbe66592209f0f5d859 Mon Sep 17 00:00:00 2001
From: Maximilian Lenkeit <2060790+mlenkeit@users.noreply.github.com>
Date: Wed, 28 Sep 2022 15:10:32 +0200
Subject: [PATCH] docs(solar): mention card color with risk level

Co-authored-by: Tim <67682506+Ein-Tim@users.noreply.github.com>
---
 solution_architecture.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/solution_architecture.md b/solution_architecture.md
index fc2f394..8b8c3f2 100644
--- a/solution_architecture.md
+++ b/solution_architecture.md
@@ -261,7 +261,7 @@ Each exposure window contains the following information:
 
 ### Risk Calculation
 
-The Exposure Windows form the foundation of the risk calculation in the app. The result is an easy-to-understand risk level that is displayed to the user: low risk (i.e. _green_) or high risk _red_. The details of the risk calculation, e.g. exposure windows or intermediate results, are not visible to the user. Further information regarding the individual exposure events (such as the matched Rolling Proximity Identifier, the Temporary Exposure Key or the exact time) remains within the secure storage of the framework and cannot be retrieved by the application.
+The Exposure Windows form the foundation of the risk calculation in the app. The result is an easy-to-understand risk level that is displayed to the user: low risk (i.e. _green_) or high risk (_red_). The details of the risk calculation, e.g. exposure windows or intermediate results, are not visible to the user. Further information regarding the individual exposure events (such as the matched Rolling Proximity Identifier, the Temporary Exposure Key or the exact time) remains within the secure storage of the framework and cannot be retrieved by the application.
 
 Within the risk calculation, the app can distinguish eight different "transmission risk levels" (TRL) of an exposure window. The TRL is a measure for the infectiousness of user of the sending app on a given day. While an exposure window already has a dedicated "infectiousness" parameter, the ENF effectively only allows two different values for it ("standard" and "high"); it cannot be used to represent eight values. The "report type" parameter has four different values and is irrelevant for the app in its original meaning (i.e. all exposures in the app are based on a "confirmed test" result). Therefore, the app uses the two possible values of the "infectiousness" parameter and the four possible values for the "report type" parameter to encode eight different TRLs. The mapping is described in _Figure 15_.