From bb2edee049937071bfdd87223d2e8f3b382d4c99 Mon Sep 17 00:00:00 2001
From: Davo1624 <85573606+Davo1624@users.noreply.github.com>
Date: Wed, 28 Dec 2022 14:44:10 -0500
Subject: [PATCH] Update alternate naming scheme

Included a bit more information on the pros and cons of using {Original Title} versus the recommended naming scheme
---
 docs/Radarr/Radarr-recommended-naming-scheme.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/Radarr/Radarr-recommended-naming-scheme.md b/docs/Radarr/Radarr-recommended-naming-scheme.md
index 9120183d5..313a2d398 100644
--- a/docs/Radarr/Radarr-recommended-naming-scheme.md
+++ b/docs/Radarr/Radarr-recommended-naming-scheme.md
@@ -45,11 +45,13 @@ If you do Anime
 
 ## Original Title vs  Original Filename
 
-If you want to keep the original release name that holds all the info of the file then I suggest to use `{Original Title}` over `{Original Filename}`
+Another option is to use  `{Original Title}` rather than the recommeneded naming scheme outlined aboove. `{Original Title}` will use the title of the release which will contain all of the information included in the release itself. The benefit of this naming scheme is to prevent download loops which can occur on import when there is a discrepancy in the release title compared to the contents of the file itself (for example, if the release title says DTS-ES but the contents are actually DTS). The downside is less flexibility with how the files are named.
+
+If using this alternate naming scheme I suggest using `{Original Title}` over `{Original Filename}`
 
 Why?
 
-The filename can be Obscured where the Release naming isn't. Especially when you use Usenet.
+The filename can be Obscured where the Release naming isn't, especially when you use Usenet.
 
 `{Original Title}` => `The.Movie.Title.2010.REMASTERED.1080p.BluRay.x264-GROUP`