Remove default icon from tip blocks that already start with an emoji

content/en/3.serveex/3.security/1.wireguard.md

@@ -218,7 +218,7 @@ sudo nano /docker/wireguard/config/wg_confs/wg0.conf
 
 Paste the downloaded configuration, then save with :kbd{value="Ctrl+O"}, :kbd{value="Enter"}, and exit with :kbd{value="Ctrl+X"}.
 
-::tip
+::tip{icon=""}
 ✨ **Alternative method:** Transfer the file via SFTP and move it:
 ```bash [Terminal]
 sudo cp ~/wg0.conf /docker/wireguard/config/wg_confs

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

@@ -66,7 +66,7 @@ services:
       retries: 3
 ```
 
-::tip
+::tip{icon=""}
 ✨ Add the Watchtower label to automate updates:
 
 ```yaml [compose.yaml]

content/en/3.serveex/3.security/4.tinyauth.md

@@ -69,7 +69,7 @@ services:
       - 3000:3000
 ```
 
-::tip
+::tip{icon=""}
 ✨ Add the Watchtower label to automate updates:
 
 ```yaml [compose.yaml]
@@ -233,7 +233,7 @@ Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ct
 
 Redeploy the TinyAuth stack. On your next visit to `https://tinyauth.mydomain.com`, you'll see a "Login with Pocket ID" option alongside the local login form.
 
-::tip
+::tip{icon=""}
 ✨ To skip straight to Pocket ID and hide the local login form, add `TINYAUTH_OAUTH_AUTOREDIRECT=pocketid` to the same `.env` file.
 ::
 

content/en/3.serveex/4.monitoring/3.speedtest-tracker.md

@@ -266,7 +266,7 @@ server {
 The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs to be on TinyAuth's Docker network to reach it by name (`tinyauth` here). This should already be set up from [exposing TinyAuth itself](/serveex/security/tinyauth#exposing-tinyauth-with-swag). If you run into an error, double-check SWAG's compose file still has that network attached.
 ::
 
-::tip
+::tip{icon=""}
 ✨ You can protect this app with [Authentik](/serveex/advanced/authentik) instead of TinyAuth by opening `speedtest.subdomain.conf` and uncommenting  
 `include /config/nginx/authentik-server.conf;` and `include /config/nginx/authentik-location.conf;`.  
 Don’t forget to [create an application and provider in Authentik](/serveex/advanced/authentik#protecting-an-app-via-reverse-proxy).

content/en/3.serveex/5.media/1.jellyfin.md

@@ -68,7 +68,7 @@ services:
       - 8096:8096
 ```
 
-::tip
+::tip{icon=""}
 ✨ Add the Watchtower label to automate updates:
 
 ```yaml [compose.yaml]

content/en/3.serveex/5.media/3.servarr.md

@@ -142,7 +142,7 @@ services:
       - 6767:6767
 ```
 
-::tip
+::tip{icon=""}
 ✨ Add the Watchtower label to each container to automate updates
 
 ```yaml [compose.yaml]
@@ -596,6 +596,6 @@ server {
 The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs to be on TinyAuth's Docker network to reach it by name (`tinyauth` here). This should already be set up from [exposing TinyAuth itself](/serveex/security/tinyauth#exposing-tinyauth-with-swag). If you run into an error, double-check SWAG's compose file still has that network attached.
 ::
 
-::tip
+::tip{icon=""}
 ✨ You can protect this app with [Authentik](/serveex/advanced/authentik) instead of TinyAuth by opening `films.subdomain.conf` and removing the `#` in front of `include /config/nginx/authentik-server.conf;`{lang=nginx} and `include /config/nginx/authentik-location.conf;`{lang=nginx}. Don't forget to [create an application and provider in Authentik](/serveex/advanced/authentik#protecting-an-app-via-reverse-proxy).
 ::

content/en/3.serveex/6.cloud/2.nextcloud.md

@@ -219,7 +219,7 @@ In Nextcloud, go to _Administration > OpenID Connect_, click the `+` button, and
 ### Done !
 ::
 
-::tip
+::tip{icon=""}
 ✨ You can use [Authentik](/serveex/advanced/authentik) instead of Pocket ID:
 
 1. In Authentik, create an application and an OAuth2/OpenID Connect provider named `Nextcloud`, with a redirect URI (type `Strict`) of `https://nextcloud.yourdomain.com/apps/user_oidc/code`.

content/en/3.serveex/7.files/2.pingvin.md

@@ -204,7 +204,7 @@ In Pingvin, go to _Administration > Configuration > Social Login_ and fill in:
 
 That's it! From now on, when you log in to Pingvin, an "Open ID" button will be available below the login form.
 
-::tip
+::tip{icon=""}
 ✨ You can use [Authentik](/serveex/advanced/authentik) instead of Pocket ID:
 
 1. In your Authentik admin area, create an OAuth2/OpenID provider.

content/en/3.serveex/8.development/1.code-server.md

@@ -60,7 +60,7 @@ services:
     restart: unless-stopped
 ```
 
-::tip
+::tip{icon=""}
 ✨ Add the Watchtower label to each container to automate updates
 
     ```yaml [compose.yaml]

content/en/3.serveex/8.development/2.forgejo.md

@@ -227,7 +227,7 @@ Also enable __Skip local 2FA__.
 ### Done !
 ::
 
-::tip
+::tip{icon=""}
 ✨ You can use [Authentik](/serveex/advanced/authentik) instead of Pocket ID:
 
 1. In Authentik, create an application and an OAuth2/OpenID Connect provider named `Forgejo`, with a redirect URI (type `Strict`) of `https://forgejo.yourdomain.com/user/oauth2/authentik/callback`.

content/en/3.serveex/9.apps/2.vaultwarden.md

@@ -293,7 +293,7 @@ Redeploy Vaultwarden. Your next visit to `https://vault.yourdomain.com` will pro
 See the [Vaultwarden SSO wiki](https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect) for the full list of options, including per-organization enforcement and master password policies.
 ::
 
-::tip
+::tip{icon=""}
 ✨ You can use [Authentik](/serveex/advanced/authentik) instead of Pocket ID:
 
 1. In Authentik, create a scope mapping named `email` with the expression `return {"email": request.user.email, "email_verified": True}` (Vaultwarden requires this claim).