From 4a934f0b7fde99db5eddd9c5e1a64ae9f9e26fa2 Mon Sep 17 00:00:00 2001
From: Stefan Melmuk <509385+stefan0xC@users.noreply.github.com>
Date: Mon, 23 Jun 2025 23:45:45 +0200
Subject: [PATCH] icon cache -> icon service

---
 Using-custom-website-icons.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Using-custom-website-icons.md b/Using-custom-website-icons.md
index 423b449..df39bbc 100644
--- a/Using-custom-website-icons.md
+++ b/Using-custom-website-icons.md
@@ -9,7 +9,7 @@ If you want to add custom icons for your website entries you can place them in t
 ![bitwarden-uri-graphic](https://github.com/user-attachments/assets/47bdf0f1-46f9-41af-8030-d0f860e2a056)  
 This means the scheme and port will be ignored when requesting icons, so you can't provide different icons based on the port number.
 
-If you are using the `internal` icon cache (the default) Vaultwarden will generally serve the icons from the `ICON_CACHE_FOLDER`.
+If you are using the `internal` icon service (the default) Vaultwarden will generally serve the icons from the `ICON_CACHE_FOLDER`.
 
 While the web-vault supports a couple of image types like ICO, BMP, GIF, JPG, WEBP and PNG, the cached icons themselves are always named `<fqdn>.png` or `<IP>.png` (eg. `data/icon_cache/en.wikipedia.org.png`). So you should name your custom icons accordingly.