diff --git a/Troubleshooting.md b/Troubleshooting.md
index 7893d78..c6f71aa 100644
--- a/Troubleshooting.md
+++ b/Troubleshooting.md
@@ -1,9 +1,13 @@
 
-## Uptime Kuma reports DOWN, but I can access.
+## Uptime Kuma reports `DOWN`, but the service can be accessed
 
-If your Uptime Kuma reports DOWN of your service, sometimes you would like to know it is a bug of Uptime Kuma or your own Docker network issue.
+> [!INFO]
+> In case you did not know: 
+> docker has [more than one network type](https://youtu.be/bKFMS5C4CG0) with only some of them allowing access to the local network and some not even allowing access to remote networks
 
-Go into your container's bash.
+If your Uptime Kuma reports `DOWN` of your service, knowing if it is a bug of Uptime Kuma / a docker network misconfiguration or a firewall is a good start to fixing the issue.
+
+To debug this, go into your container's bash via
 
 ```bash
 docker exec -it uptime-kuma bash
@@ -15,7 +19,9 @@ Install `curl`
 apt update && apt --yes install curl
 ```
 
-Then you can test with these commands for example:
+Then you can debug this issue with commands like `ping`, `curl`, ...
+Examples:
+
 ```bash
 curl https://google.com
 ping google.com