diff --git a/docs/troubleshooting.rst b/docs/troubleshooting.rst
index 571b4dd4..cf06cfc3 100644
--- a/docs/troubleshooting.rst
+++ b/docs/troubleshooting.rst
@@ -11,20 +11,19 @@ Please also have a look at `Open Issues <https://https://github.com/SafeExamBrow
 - **Version**     : 1.3.x
 - **Domain**      : Exam Monitoring
 - **Problem**     : SEB connections get lost and ping-times go up for already connected SEB clients
-- **Explanation** : This issue is due to a access token used by SEB client to authenticate on SEB Server that lasts not longer the
-one hour since SEB Server version 1.3 and since SEB client has no new access token request implements yet.
-- **Solution**    : A workaround for SEB Server version 1.3.x is to make the access token expiry-date last long enough to minimize the possibility
-that the access token became invalid during a exam. We recommend to set it to 12 hours = 43200 seconds. Therefore please set the following 
-SEB Server setup properties in the respective application-prod.properties configuration file of your SEB Server setup:
+- **Explanation** : This issue is due to a access token used by SEB client to authenticate on SEB Server that lasts not longer the one hour since SEB Server version 1.3 and since SEB client has no new access token request implements yet.
+- **Solution**    : A workaround for SEB Server version 1.3.x is to make the access token expiry-date last long enough to minimize the possibility that the access token became invalid during a exam. We recommend to set it to 12 hours = 43200 seconds. Therefore please set the following  SEB Server setup properties in the respective application-prod.properties configuration file of your SEB Server setup:
 
-sebserver.webservice.api.admin.accessTokenValiditySeconds=43200
-sebserver.webservice.api.exam.accessTokenValiditySeconds=43200
+    sebserver.webservice.api.admin.accessTokenValiditySeconds=43200
+    sebserver.webservice.api.exam.accessTokenValiditySeconds=43200
 
-In SEB Server version 1.4 this is already set as default again and we are currently working on new SEB client versions that also 
-handle SEB Server communication token expiry by automatically requesting a new access token (with new lifetime) from SEB Server
-when an old access token is not valid any longer.
+    In SEB Server version 1.4 this is already set as default again and we are currently working on new SEB client versions that also 
+    handle SEB Server communication token expiry by automatically requesting a new access token (with new lifetime) from SEB Server
+    when an old access token is not valid any longer.
 
 --------------------------------
+
+
 --------------------------------
 
 - **Version**     : 1.0.0