1 files changed, 4 insertions, 4 deletions
diff --git a/docs/customservices.md b/docs/customservices.md
index 9317907..7e3e6b3 100644
--- a/docs/customservices.md
+++ b/docs/customservices.md
@@ -67,18 +67,18 @@ Two lines are needed in the config.yml :
 The url must be the root url of Medusa application.
 The Medusa API key can be found in General configuration > Interface. It is needed to access Medusa API.
-## Lidarr, Sonarr and Radarr
+## Lidarr, Prowlarr, Sonarr and Radarr
 This service displays Activity (blue), Warning (orange) or Error (red) notifications bubbles from the Lidarr, Radarr or Sonarr application.
 Two lines are needed in the config.yml :
 ```yaml
-  type: "Lidarr", "Radarr" or "Sonarr"
+  type: "Lidarr", "Prowlarr", "Radarr" or "Sonarr"
  apikey: "01234deb70424befb1f4ef6a23456789"
 ```
-The url must be the root url of Lidarr, Radarr or Sonarr application.
+The url must be the root url of Lidarr, Prowlarr, Radarr or Sonarr application.
-The Lidarr, Radarr or Sonarr API key can be found in Settings > General. It is needed to access the API.
+The Lidarr, Prowlarr, Radarr or Sonarr API key can be found in Settings > General. It is needed to access the API.
 If you are using an older version of Radarr or Sonarr which don't support the new V3 api endpoints, add the following line to your service config "legacyApi: true", example: 
 ```yaml

diff --git a/docs/customservices.md b/docs/customservices.md index 9317907..7e3e6b3 100644 --- a/docs/customservices.md +++ b/docs/customservices.md
@@ -67,18 +67,18 @@ Two lines are needed in the config.yml :
67	The url must be the root url of Medusa application.	67	The url must be the root url of Medusa application.
68	The Medusa API key can be found in General configuration > Interface. It is needed to access Medusa API.	68	The Medusa API key can be found in General configuration > Interface. It is needed to access Medusa API.
69		69
70	## Lidarr, Sonarr and Radarr	70	## Lidarr, Prowlarr, Sonarr and Radarr
71		71
72	This service displays Activity (blue), Warning (orange) or Error (red) notifications bubbles from the Lidarr, Radarr or Sonarr application.	72	This service displays Activity (blue), Warning (orange) or Error (red) notifications bubbles from the Lidarr, Radarr or Sonarr application.
73	Two lines are needed in the config.yml :	73	Two lines are needed in the config.yml :
74		74
75	```yaml	75	```yaml
76	type: "Lidarr", "Radarr" or "Sonarr"	76	type: "Lidarr", "Prowlarr", "Radarr" or "Sonarr"
77	apikey: "01234deb70424befb1f4ef6a23456789"	77	apikey: "01234deb70424befb1f4ef6a23456789"
78	```	78	```
79		79
80	The url must be the root url of Lidarr, Radarr or Sonarr application.	80	The url must be the root url of Lidarr, Prowlarr, Radarr or Sonarr application.
81	The Lidarr, Radarr or Sonarr API key can be found in Settings > General. It is needed to access the API.	81	The Lidarr, Prowlarr, Radarr or Sonarr API key can be found in Settings > General. It is needed to access the API.
82	If you are using an older version of Radarr or Sonarr which don't support the new V3 api endpoints, add the following line to your service config "legacyApi: true", example:	82	If you are using an older version of Radarr or Sonarr which don't support the new V3 api endpoints, add the following line to your service config "legacyApi: true", example:
83		83
84	```yaml	84	```yaml