From af9cb3782bdacc5c95f23e4645ae4f2706c41afc Mon Sep 17 00:00:00 2001
From: GPclips <14160706+GPclips@users.noreply.github.com>
Date: Wed, 30 Sep 2020 10:20:23 +0200
Subject: [PATCH] Update cwa-risk-assessment.md

Corrected the suggestion of @pdehaye based on the video of @kbobrowski: https://www.youtube.com/watch?v=SAi24ctpyZQ
---
 cwa-risk-assessment.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cwa-risk-assessment.md b/cwa-risk-assessment.md
index 6b23e20..f6bfec9 100644
--- a/cwa-risk-assessment.md
+++ b/cwa-risk-assessment.md
@@ -46,7 +46,7 @@ This notification takes place in the CWA and, at the same time, provides recomme
 
 When assessing the times and distances calculated by the CWA, it is important to consider that it is not possible to measure these two parameters precisely.
 The individually measured times can deviate from the actual encounter time by 5 minutes plus or minus and the calculated distances are approximate values under ideal conditions, that is, without any impediments between the two smartphones.
-Even minor impediments, such as a person between the two smartphones or a signal-impeding smartphone case, can cause the distance to appear to be twice as large as it actually is.
+Even minor impediments, such as a person between the two smartphones or a signal-impeding smartphone case, can cause the distance to appear to be ten times as large as it actually is.
 
 Due to privacy considerations, the properties described above can currently only be queried for the total set of all risk exposures at the interface to the operating system, but not for individual risk exposures or exposure by day.
 As long as the number of new infections remains relatively low, this should not make much of a difference, because it is likely that only very few CWA users will have been exposed to multiple persons who have tested positive within the time frame until they are notified.