diff --git a/docs/super-states.html b/docs/super-states.html
index e818c38ef2b9f296c36b5823365f014c9c5ab6af..a5a01148d7e72995c6612c396f17f977e81d4f1b 100644
--- a/docs/super-states.html
+++ b/docs/super-states.html
@@ -76,7 +76,7 @@
     <td>Tooltip: <code>Es ist ein Fehler aufgetreten!</code></td>
   </tr>
    <tr>
-    <td>An error has occurred a the participants computer. Probably a network error or the like, but can also indicate bugs and should be investigated if possible. The participant should reload his browser and try if the problem still exists.</td>
+    <td>An error has occurred a the participants computer. Probably a network error or the like, but can also indicate bugs and should be investigated if possible. The participant should reload his browser and get support if the problem still exists.</td>
   </tr>
 </table>
 <br>
@@ -146,7 +146,7 @@
     <td>Tooltip: <code>Test ist 5 Minuten oder länger inaktiv!</code></td>
   </tr>
    <tr>
-    <td>The participant was idle for five minutes or longer.</td>
+    <td>The participant was idle for five minutes or longer. This state can only be displayed on polling mode and is intended to be a fallback for the case that the participant's browser or computer was shut down and not able to report the lost connection. It' s not appropriate to measure testees behaviour.</td>
   </tr>
 </table>
 <br>
@@ -188,7 +188,7 @@
     <td>Tooltip: <code>Test läuft</code></td>
   </tr>
    <tr>
-    <td>Test seems to run but the connection type is unknown. This is is more or less a fallback state which indicates, that we know nothing about the test except for it's existence. This could be the case in various error-scenarios or misconfigurations, and should normally not be the case. It should be investigated,but most likely the test can be continued anyway since the error is more likely on the monitor's side.</td>
+    <td>Test seems to run but the connection type is unknown. This is is more or less a fallback state which indicates, that nothing is known about the test except for it's existence. This could be the case in various error-scenarios or misconfigurations but should not happen in general. It should be investigated, but most likely the test can be continued safely since the error is more likely on the monitor's side.</td>
   </tr>
 </table>
 <br>
diff --git a/src/app/group-monitor/test-session/super-states.js b/src/app/group-monitor/test-session/super-states.js
index cf5814daa7a5a34d531c50198dc1c3a7da6053c8..2f687d30d8de3aea55594e5c8ceca014f6a18afd 100644
--- a/src/app/group-monitor/test-session/super-states.js
+++ b/src/app/group-monitor/test-session/super-states.js
@@ -16,7 +16,7 @@ exports.superStates = {
     class: 'danger',
     description: 'An error has occurred a the participants computer. Probably a network error or the like, ' +
       'but can also indicate bugs and should be investigated if possible. The participant should reload ' +
-      'his browser and try if the problem still exists.'
+      'his browser and get support if the problem still exists.'
   },
   controller_terminated: {
     tooltip: 'Testausführung wurde beendet und kann wieder aufgenommen werden. ' +
@@ -46,7 +46,9 @@ exports.superStates = {
   idle: {
     tooltip: 'Test ist 5 Minuten oder länger inaktiv!',
     icon: 'hourglass_full',
-    description: 'The participant was idle for five minutes or longer.'
+    description: 'The participant was idle for five minutes or longer. This state can only be displayed on polling ' +
+      'mode and is intended to be a fallback for the case that the participant\'s browser or computer was shut down ' +
+      'and not able to report the lost connection. It\' s not appropriate to measure testees behaviour.'
   },
   connection_websocket: {
     tooltip: 'Test läuft, Verbindung ist live',
@@ -67,8 +69,8 @@ exports.superStates = {
     tooltip: 'Test läuft',
     icon: 'play_circle_filled',
     description: 'Test seems to run but the connection type is unknown. This is is more or less a fallback state ' +
-      'which indicates, that we know nothing about the test except for it\'s existence. This could be the case in ' +
-      'various error-scenarios or misconfigurations, and should normally not be the case. It should be investigated,' +
-      'but most likely the test can be continued anyway since the error is more likely on the monitor\'s side.'
+      'which indicates, that nothing is known about the test except for it\'s existence. This could be the case in ' +
+      'various error-scenarios or misconfigurations but should not happen in general. It should be investigated, ' +
+      'but most likely the test can be continued safely since the error is more likely on the monitor\'s side.'
   }
 };