diff --git a/Reverse-Proxy.md b/Reverse-Proxy.md
index e0f5b09..410e0dc 100644
--- a/Reverse-Proxy.md
+++ b/Reverse-Proxy.md
@@ -9,9 +9,10 @@ Uptime Kuma **do not supported on subdirectory** reverse proxy. Please prepare a
 - [Caddy](#caddy)
 - [Nginx Proxy Manager](#nginx-proxy-manager)
 - [Synology Builtin Reverse Proxy](#synology-builtin-reverse-proxy)
-- [Cloudflare](#cloudflare)
-- [SSL/HTTPS](#ssl-https)
 - [Traefik](#Traefik)
+- [Cloudflare](#cloudflare)
+- Others
+  - [SSL/HTTPS](#sslhttps)
 
 
 # Nginx
@@ -100,23 +101,6 @@ Please enable "WebSockets Supports"
 
 https://mlohr.com/websockets-for-synology-dsm/
 
-# Cloudflare
-
-You must enable "WebSockets" in Cloudflare Dashboard:
-
-Cloudflare Dashboard -> Network -> Enable WebSockets
-
-Read more:
-https://github.com/louislam/uptime-kuma/issues/138#issuecomment-890485229
-
-
-# SSL/HTTPS
-
-It is recommended to use SSL(HTTPS) with your web-server to avoid MiTM attacks when on a public network. If using caddy these certificates will be auto-generated by caddy and will keep them updated.
-
-If your using Apache or NGINX, it is recommended to use CertBot to manage SSL for free, it uses Let's Encrypt to get it's certificates and keeps them renewed. You can also use your own Certificates and place them as shown above. If using cerbot use the "Without SSL" settings and then run certbot on it and it will automatically configure auto-HTTPS redirection.
-
-
 # Traefik
 ```
 labels:
@@ -128,3 +112,20 @@ labels:
     - "traefik.http.services.uptime-kuma.loadBalancer.server.port=3001"
 ```
 Add the above, to your Docker-compose.yml file, and replace "YourOwnHostname" with the hostname you want to use, to use Traefik reverse Proxy. Note setup correct, Traefik can automaticly, get a Let's Encrypt certificate for your service. 
+
+# Cloudflare
+
+You must enable "WebSockets" in Cloudflare Dashboard:
+
+Cloudflare Dashboard -> Network -> Enable WebSockets
+
+Read more:
+https://github.com/louislam/uptime-kuma/issues/138#issuecomment-890485229
+
+# Others
+
+## SSL/HTTPS
+
+It is recommended to use SSL(HTTPS) with your web-server to avoid MiTM attacks when on a public network. If using caddy these certificates will be auto-generated by caddy and will keep them updated.
+
+If your using Apache or NGINX, it is recommended to use CertBot to manage SSL for free, it uses Let's Encrypt to get it's certificates and keeps them renewed. You can also use your own Certificates and place them as shown above. If using cerbot use the "Without SSL" settings and then run certbot on it and it will automatically configure auto-HTTPS redirection.