From 1679f7132a3f3ebe4366b736d072ed3a3d9fd378 Mon Sep 17 00:00:00 2001
From: ilike2burnthing <59480337+ilike2burnthing@users.noreply.github.com>
Date: Wed, 18 May 2022 04:09:29 +0100
Subject: [PATCH] Updated Renaming Indexers (markdown)

---
 Renaming-Indexers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Renaming-Indexers.md b/Renaming-Indexers.md
index 330d18d..4a963da 100644
--- a/Renaming-Indexers.md
+++ b/Renaming-Indexers.md
@@ -10,7 +10,7 @@ Note that changing the id must be justified.
    * c#: rename the file and the class name (not need to change `src/Jackett.Updater/Program.cs`)
 4. Optional: The tracker name / description is not related to the id and it can be changed anytime
 
-## How does it works for the user
+## How it works for the user
 1. The updater will remove the old .yaml definition (if it's a .yaml indexer) and the new one will be extracted in the folder.
 2. In the first start, Jackett will rename the old configuration file into the new one. The user will see this trace. `Info Configuration renamed: /home/XX/.config/Jackett/Indexers/nostalgic.json => /home/XX/.config/Jackett/Indexers/vhstapes.json `
 3. The indexer is able to load the previous configuration without problem. From this moment, there are no longer remains of the old id.