Merge branch 'master' of https://github.com/TRaSH-Guides/Guides

docs/Hardlinks/How-to-setup-for/Synology.md

@@ -163,7 +163,7 @@ Your application data will be stored in the `docker` share in the folder called
 Create these folders with command below, or create them in File Station manually.
 
 ```bash
-mkdir -p /volume1/docker/appdata/{radarr,sonarr,bazarr,plex,pullio}
+mkdir -p /volume1/docker/appdata/{radarr,sonarr,bazarr,plex,prowlarr,pullio}
 ```
 
 You can add your own subfolders for your download client(s) using the command above, by adding the name to the command.
@@ -177,6 +177,7 @@ docker
     ├── sonarr
     ├── bazarr
     ├── plex
+    ├── prowlarr
     ├── pullio
     ├── (your download client, i.e. nzbget; sabnzbd; qbittorrent)
     └── (other applications)
@@ -210,6 +211,7 @@ This docker-compose file will have the following docker containers included.
     - Sonarr
     - Bazarr (Subtitle searcher and downloader)
     - Plex
+    - Prowlarr (indexer/tracker manager)
 ```
 
 What's not included (and where are the download clients?).

docs/Radarr/Radarr-collection-of-custom-formats.md

@@ -540,7 +540,7 @@ We've made 3 guides related to this.
 
     --8<-- "includes/cf-descriptions/dv.md"
 
-<! -- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md` -->
+<!-- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md` -->
 
 ??? example "JSON - [Click to show/hide]"
 

docs/Sonarr/sonarr-collection-of-custom-formats.md

@@ -541,7 +541,7 @@ We've made 3 guides related to this.
 
     --8<-- "includes/cf-descriptions/dv.md"
 
-<! -- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md`-->
+<!-- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md`-->
 
 ??? example "JSON - [Click to show/hide]"