2.5.2 docs (#247)

* docs: Changes for v2.5.2 release

* docs: Remove -X POST

Curl automatically uses POST for -d and --data-binary.

I intentionally left it in to be explicit to learners, but
maybe best practices are better.

* api: /adapt endpoint and Etag usage

* api: Minor tweaks

* Alright fine

* Clarify Etag usage

* CEL embedded matchers

* Oops

* Lots more adjustments

Co-authored-by: Francis Lavoie <lavofr@gmail.com>

src/docs/markdown/quick-starts/api.md

@@ -17,7 +17,6 @@ First start Caddy:
 Caddy is currently running idle (with a blank configuration). Give it a simple config with `curl`:
 
 <pre><code class="cmd bash">curl localhost:2019/load \
-    -X POST \
     -H "Content-Type: application/json" \
     -d @- << EOF
     {
@@ -44,7 +43,6 @@ EOF</code></pre>
 Giving a POST body with [Heredoc](https://en.wikipedia.org/wiki/Here_document#Unix_shells) can be tedious, so if you prefer to use files, save the JSON to a file called `caddy.json` and then use this command instead:
 
 <pre><code class="cmd bash">curl localhost:2019/load \
-  -X POST \
   -H "Content-Type: application/json" \
   -d @caddy.json
 </code></pre>

src/docs/markdown/quick-starts/caddyfile.md

@@ -13,9 +13,12 @@ localhost
 ```
 
 <aside class="tip">
-	If the HTTP and HTTPS ports (80 and 443, respectively) are privileged ports on your OS, you will either need to run with elevated privileges or use a higher port. To use a higher port, just change the address to something like <code>localhost:2015</code> and change the HTTP port using the <a href="/docs/caddyfile/options">http_port</a> Caddyfile option.
+
+If the HTTP and HTTPS ports (80 and 443, respectively) are privileged ports on your OS, you will either need to run with elevated privileges or use a higher port. To use a higher port, just change the address to something like `localhost:2015` and change the HTTP port using the [`http_port`](/docs/caddyfile/options) Caddyfile option.
+
 </aside>
 
+
 Then hit enter and type what you want it to do, so it looks like this:
 
 ```caddy
@@ -56,7 +59,6 @@ localhost:2016 {
 You can give Caddy the updated configuration two ways, either with the API directly:
 
 <pre><code class="cmd bash">curl localhost:2019/load \
-	-X POST \
 	-H "Content-Type: text/caddyfile" \
 	--data-binary @Caddyfile
 </code></pre>
@@ -78,4 +80,4 @@ When you are done with Caddy, make sure to stop it:
 
 - [Common patterns](/docs/caddyfile/patterns)
 - [Caddyfile concepts](/docs/caddyfile/concepts)
-- [Directives](/docs/caddyfile/directives)
+- [Directives](/docs/caddyfile/directives)

src/docs/markdown/quick-starts/https.md

@@ -30,7 +30,9 @@ Before continuing, verify correct records with an authoritative lookup. Replace
 
 Also make sure your server is externally reachable on ports 80 and 443 from a public interface.
 
-<aside class="tip">If you're on your home or other restricted network, you may need to forward ports or adjust firewall settings.</aside>
+<aside class="tip">
+	If you're on your home or other restricted network, you may need to forward ports or adjust firewall settings.
+</aside>
 
 All we have to do is start Caddy with your domain name in the config. There are several ways to do this.