Add Uptime-Kuma introduction, write descriptive alt text site-wide, and fix brand capitalization and filenames with spaces

content/en/3.serveex/3.security/4.pocket-id.md

@@ -96,7 +96,7 @@ TRUST_PROXY=true
 |----------|-------|---------|
 | `APP_URL`{lang=properties} | The public URL you'll use to reach Pocket ID (see exposure below) | `https://id.mydomain.com` |
 | `ENCRYPTION_KEY`{lang=properties} | The key generated above | `Q2pVEqsTNRkJSO9SkJzU3KZ2...` |
-| `TRUST_PROXY`{lang=properties} | Required since Pocket ID sits behind Swag | `true` |
+| `TRUST_PROXY`{lang=properties} | Required since Pocket ID sits behind SWAG | `true` |
 
 Deploy the stack. The local interface is available at `http://yourserverip:1411`.
 
@@ -114,7 +114,7 @@ Pocket ID doesn't use passwords: your first account is created with a **passkey*
 Passkeys require a secure context: HTTPS, or `localhost`. Registering one from `http://yourserverip:1411` on another machine will be refused by the browser, since that's plain HTTP to a non-`localhost` address. If setup doesn't complete locally, expose Pocket ID first (see below) and finish setup over HTTPS instead.
 ::
 
-## Exposing Pocket ID with Swag
+## Exposing Pocket ID with SWAG
 Other apps need to reach Pocket ID over HTTPS to complete the OIDC login flow, so it must be exposed even if you only use it from home.
 
 ::note
@@ -153,7 +153,7 @@ Here we assume the Pocket ID network name is `pocket-id_default`. You can check
 
 ### Create the subdomain.conf file
 
-In the Swag folders, create the file `id.subdomain.conf`:
+In the SWAG folders, create the file `id.subdomain.conf`:
 
 ::tip{icon="" to="/serveex/files/file-browser-quantum"}
 ✨ __Tip:__ Use **File Browser Quantum** to navigate and edit files instead of using terminal commands.