🔧 Update docs setup with latest configs and plugins (#11953)

docs/en/docs/deployment/https.md

@@ -4,8 +4,11 @@ It is easy to assume that HTTPS is something that is just "enabled" or not.
 
 But it is way more complex than that.
 
-!!! tip
-    If you are in a hurry or don't care, continue with the next sections for step by step instructions to set everything up with different techniques.
+/// tip
+
+If you are in a hurry or don't care, continue with the next sections for step by step instructions to set everything up with different techniques.
+
+///
 
 To **learn the basics of HTTPS**, from a consumer perspective, check <a href="https://howhttps.works/" class="external-link" target="_blank">https://howhttps.works/</a>.
 
@@ -68,8 +71,11 @@ In the DNS server(s) you would configure a record (an "`A record`") to point **y
 
 You would probably do this just once, the first time, when setting everything up.
 
-!!! tip
-    This Domain Name part is way before HTTPS, but as everything depends on the domain and the IP address, it's worth mentioning it here.
+/// tip
+
+This Domain Name part is way before HTTPS, but as everything depends on the domain and the IP address, it's worth mentioning it here.
+
+///
 
 ### DNS
 
@@ -115,8 +121,11 @@ After this, the client and the server have an **encrypted TCP connection**, this
 
 And that's what **HTTPS** is, it's just plain **HTTP** inside a **secure TLS connection** instead of a pure (unencrypted) TCP connection.
 
-!!! tip
-    Notice that the encryption of the communication happens at the **TCP level**, not at the HTTP level.
+/// tip
+
+Notice that the encryption of the communication happens at the **TCP level**, not at the HTTP level.
+
+///
 
 ### HTTPS Request