From 62da87b1cbc443f92b338e8d1d08b23ceb102166 Mon Sep 17 00:00:00 2001
From: Opt6 <82363306+Opt6@users.noreply.github.com>
Date: Mon, 3 May 2021 10:29:00 -0700
Subject: [PATCH] Updated link to Docker guide

---
 Downloads-and-Importing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Downloads-and-Importing.md b/Downloads-and-Importing.md
index 3962637..1d9e832 100644
--- a/Downloads-and-Importing.md
+++ b/Downloads-and-Importing.md
@@ -27,7 +27,7 @@ The default user for a Windows service is **SYSTEM** which typically doesn't hav
 While mapped network drives like `X:\` are convenient, they aren't as reliable as UNC paths like `\\server\share` and they're also not available before login. Setup Sonarr and your download client(s) so that they use UNC paths as needed. If your library is on a share, you'd make sure your root folders are using UNC paths. If your download client sends to a share, that is where you'll need to configure UNC paths since Sonarr gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don't use them for automation.
 
 ## Docker and user, group, ownership, permissions and paths
-Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [for these automation software and Docker](https://old.reddit.com/r/usenet/wiki/docker) which is all about user, group, ownership, permissions and paths. It isn't specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.
+Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [for these automation software and Docker](https://wiki.servarr.com/Docker_Guide) which is all about user, group, ownership, permissions and paths. It isn't specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.
 
 ## Download client clearing items
 The download client should *not* be responsible for removing downloads. Usenet clients should be configured so they *don't* remove downloads from history. Torrent clients should be setup so they *don't* remove torrents when they're finished seeding (pause or stop instead). This is because Sonarr communicates with the download client to know what to import, so if they're *removed* there is nothing to be imported... even if there is a folder full of files.